# HG changeset patch
# User Maxim Konovalov <maxim@nginx.com>
# Date 1486987543 0
# Node ID 862e96a39fe31ad21efd9bbc68e16f237d2a4a07
# Parent  02dedcb347e58f9b99d4148f42fecf4a2a025238
Typo fixed.

diff -r 02dedcb347e5 -r 862e96a39fe3 xml/en/docs/dev/development_guide.xml
--- a/xml/en/docs/dev/development_guide.xml	Fri Feb 10 13:02:14 2017 +0300
+++ b/xml/en/docs/dev/development_guide.xml	Mon Feb 13 12:05:43 2017 +0000
@@ -1095,7 +1095,7 @@
 destroyed.
 Pool is usually tied with a specific nginx object (like HTTP request) and
 destroyed in the end of that object’s lifetime, releasing the object itself.
-Registering a pool cleanup is a convinient way to release resources, close file
+Registering a pool cleanup is a convenient way to release resources, close file
 descriptors or make final adjustments to shared data, associated with the main
 object.
 </para>