summary refs log tree commit diff
path: root/manual
diff options
context:
space:
mode:
authorJim Meyering <meyering@redhat.com>2008-06-04 11:46:50 +0200
committerJim Meyering <meyering@redhat.com>2010-02-22 21:26:11 +0100
commit82acaacb9c7689c479c3426743ae66d0ad466a1d (patch)
treed941360c573b98b03573c7cbd1611628fea2cd5d /manual
parentbbf70ae9ce646540576f2b0cbc66b90da1511b0b (diff)
downloadglibc-82acaacb9c7689c479c3426743ae66d0ad466a1d.tar.gz
glibc-82acaacb9c7689c479c3426743ae66d0ad466a1d.tar.xz
glibc-82acaacb9c7689c479c3426743ae66d0ad466a1d.zip
manual: adjust grammar
* manual/charset.texi: Adjust grammar.
Diffstat (limited to 'manual')
-rw-r--r--manual/charset.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/manual/charset.texi b/manual/charset.texi
index a49798c7c2..808469b8c1 100644
--- a/manual/charset.texi
+++ b/manual/charset.texi
@@ -393,7 +393,7 @@ We already said above that the currently selected locale for the
 by the functions we are about to describe.  Each locale uses its own
 character set (given as an argument to @code{localedef}) and this is the
 one assumed as the external multibyte encoding.  The wide character
-set always is UCS-4, at least on GNU systems.
+set is always UCS-4, at least on GNU systems.
 
 A characteristic of each multibyte character set is the maximum number
 of bytes that can be necessary to represent one character.  This
@@ -577,8 +577,8 @@ The @code{btowc} function was introduced in @w{Amendment 1} to @w{ISO C90}
 and is declared in @file{wchar.h}.
 @end deftypefun
 
-Despite the limitation that the single byte value always is interpreted
-in the initial state this function is actually useful most of the time.
+Despite the limitation that the single byte value is always interpreted
+in the initial state, this function is actually useful most of the time.
 Most characters are either entirely single-byte character sets or they
 are extension to ASCII.  But then it is possible to write code like this
 (not that this specific example is very useful):
@@ -607,10 +607,10 @@ that there is no guarantee that one can perform this kind of arithmetic
 on the character of the character set used for @code{wchar_t}
 representation.  In other situations the bytes are not constant at
 compile time and so the compiler cannot do the work.  In situations like
-this it is necessary @code{btowc}.
+this, using @code{btowc} is required.
 
 @noindent
-There also is a function for the conversion in the other direction.
+There is also a function for the conversion in the other direction.
 
 @comment wchar.h
 @comment ISO