- Nicer version

diff --git a/README.UNICODE-UPGRADES b/README.UNICODE-UPGRADES
index dba7fd38894bd17e38d0770d4dd6e2055ac2276a..674eaa635942c93ba7177159d6e8737c73d368f0 100644 (file)
--- a/README.UNICODE-UPGRADES
+++ b/README.UNICODE-UPGRADES
@@ -541,12 +541,12 @@ Unicode strings:
             Z_OBJCE_P(object)->name);
 
 Since [v]spprintf() can only output native strings there are also the new
-function [v]uspprintf() and [v]zspprintf() that create unicode strings and
+functions [v]uspprintf() and [v]zspprintf() that create unicode strings and
 return the number of characters printed. That is they return the length rather 
-than the byte size. The second pair offunction also takes an additional type
+than the byte size. The second pair of functions also takes an additional type
 parameter that allows to create a string of arbitrary type. The following
 example illustrates the use. Assume it fetches a unicode/native string into
-path, path_len, path_type and then creates sub_name, sub_len and sub_type.
+path, path_len and path_type inorder to create sub_name, sub_len and sub_type.
 
        zstr path, sub_name;
        int path_len, sub_len;