Algorithm-box
diff --git a/‎open_function.rst‎
Lines changed: 13 additions & 13 deletions b/‎open_function.rst‎
Lines changed: 13 additions & 13 deletions
@@ -1,4 +1,4 @@
-Open function
+``open`` Function
 -------------
 
 `open <http://docs.python.org/dev/library/functions.html#open>`__ opens
@@ -17,18 +17,18 @@ you spot them all? If not, read on. By the end of this article, you'll
 know what's wrong in the above code, and, more importantly, be able to
 avoid these mistakes in your own code. Let's start with the basics:
 
-The return of open is a file handle, given out from the operating system
+The return value from ``open`` is a file handle, given out from the operating system
 to your Python application. You will want to return this file handle
 once you're finished with the file, if only so that your application
-won't reach the limit of the number of open file handle it can have at
+won't reach the limit of the number of open file handles it can have at
 once.
 
 Explicitly calling ``close`` closes the file handle, but only if the
 read was successful. If there is any error just after ``f = open(...)``,
 ``f.close()`` will not be called (depending on the Python interpreter,
 the file handle may still be returned, but that's another story). To
 make sure that the file gets closed whether an exception occurs or not,
-pack it into a ```with`` statement:
+pack it into a ``with`` statement:
 
 .. code:: python
 
@@ -53,28 +53,28 @@ or text mode (a string of characters).
 
 In general, if the format is written by humans, it tends to be text
 mode. ``jpg`` image files are not generally written by humans (and are
-indeed not readable to humans), and you should therefore open them in
-binary mode by adding a ``b`` to the text string (if you're following
+indeed not readable by humans), and you should therefore open them in
+binary mode by adding a ``b`` to the mode string (if you're following
 the opening example, the correct mode would be ``rb``). If you open
 something in text mode (i.e. add a ``t``, or nothing apart from
-``r/r+/w/a``), you must also know which encoding to use - for a
+``r/r+/w/a``), you must also know which encoding to use. For a
 computer, all files are just bytes, not characters.
 
 Unfortunately, ``open`` does not allow explicit encoding specification
 in Python 2.x. However, the function
 `io.open <http://docs.python.org/2/library/io.html#io.open>`__ is
 available in both Python 2.x and 3.x (where it is an alias of ``open``),
 and does the right thing. You can pass in the encoding with the
-``encoding`` keyword. If you don't pass in any encoding, a system- (and
-Python-) specific default will be picked. You may be tempted to rely on
+``encoding`` keyword. If you don't pass in any encoding, a system -- and
+Python -- specific default will be picked. You may be tempted to rely on
 these defaults, but the defaults are often wrong, or the default
-encoding cannot actually express all characters (this will happen on
+encoding cannot actually express all characters in the file (this will happen often on
 Python 2.x and/or Windows). So go ahead and pick an encoding. ``utf-8``
 is a terrific one. When you write a file, you can just pick the encoding
 to your liking (or the liking of the program that will eventually read
 your file).
 
-How do you find out which encoding a file you read has? Well,
+How do you find out which encoding a file you're reading was written in? Well,
 unfortunately, there is no foolproof way to detect the encoding - the
 same bytes can represent different, but equally valid characters in
 different encodings. Therefore, you must rely on metadata (for example,
@@ -93,11 +93,11 @@ determines whether it's JPG (hint: These files start with the bytes
         jpgdata = inf.read()
 
     if jpgdata.startswith(b'\xff\xd8'):
-        text = u'This is a jpeg file (%d bytes long)\n'
+        text = u'This is a JPEG file (%d bytes long)\n'
     else:
         text = u'This is a random file (%d bytes long)\n'
 
     with io.open('summary.txt', 'w', encoding='utf-8') as outf:
         outf.write(text % len(jpgdata))
 
-I am sure that now you would use ``open`` correctly!
+I am sure that now you will use ``open`` correctly!