Fix typos.
This commit is contained in:
parent
61cb395f24
commit
6d8ec98027
|
@ -32,7 +32,7 @@ Unicode-based internal representation, making it difficult to ignore
|
|||
the encoding of byte strings in the same way that the C interfaces can
|
||||
ignore the encoding.
|
||||
|
||||
On the other hand, Microsoft Windows NT has correct the original
|
||||
On the other hand, Microsoft Windows NT has corrected the original
|
||||
design limitation of Unix, and made it explicit in its system
|
||||
interfaces that these data (file names, environment variables, command
|
||||
line arguments) are indeed character data, by providing a
|
||||
|
@ -94,7 +94,7 @@ will produce non-sensical data.
|
|||
|
||||
For most applications, we assume that they eventually pass data
|
||||
received from a system interface back into the same system
|
||||
interfaces. For example, and application invoking os.listdir() will
|
||||
interfaces. For example, an application invoking os.listdir() will
|
||||
likely pass the result strings back into APIs like os.stat() or
|
||||
open(), which then encodes them back into their original byte
|
||||
representation. Applications that need to process the original byte
|
||||
|
|
Loading…
Reference in New Issue