From 26adc6f028b5e92bd8767f1367c97e46470b9762 Mon Sep 17 00:00:00 2001 From: Stefan Behnel Date: Sat, 12 Oct 2013 10:19:06 +0200 Subject: [PATCH] fix typos --- docs/src/tutorial/memory_allocation.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/tutorial/memory_allocation.rst b/docs/src/tutorial/memory_allocation.rst index c995d0e..b15ec0e 100644 --- a/docs/src/tutorial/memory_allocation.rst +++ b/docs/src/tutorial/memory_allocation.rst @@ -67,7 +67,7 @@ when they are no longer used (and *must* always use the matching type of free function). Otherwise, they won't be reclaimed until the python process exits. This is called a memory leak. -If a chuck of memory needs a larger lifetime then can be managed by a +If a chunk of memory needs a larger lifetime than can be managed by a ``try..finally`` block, another helpful idiom is to tie its lifetime to a Python object to leverage the Python runtime's memory management, e.g.:: -- 2.7.4