URL: http://docs.python.org/tut/node3.html 
 
In the first paragraph, it says: 
"[snip] or the feature involves a system call or other function that is 
only accessible from C ...Usually the problem [snip]" 
 
The typo: "[snip] C ...Usually [snip]" 
The space after 'C' should be removed, and one should be added 
before 'Usually', so it becomes: "[snip] C... Usually [snip]". 
 
I admit it's not a really big problem, but it's not hard to solve either, I 
guess. 

Logged In: YES 
user_id=313612

I'm not too sure what I should do with another error in the tutorial... I 
guess starting a new bugreport each time for stuff like simple typos would 
be overkill, so maybe it's just easier to attach (an)other error(s) here? 
If you prefer a new bugreport, please tell me. 
 
Anyway, on to the actual "error"... 
URL: http://docs.python.org/tut/node4.html 
Part: 2.2.2 Executable Python Scripts 
Sentence: "The script can be given a executable mode, or permission, using 
the chmod command:" 
Should be: "aN executable mode", AFAIK. 

Logged In: YES 
user_id=313612

URL: http://docs.python.org/tut/node5.html 
Part: 3.1.3 Unicode Strings  
Sentence: "Previously, there were only 256 possible ordinals for script 
characters and texts were typically bound to a code page which mapped 
the ordinals to script characters." 
 
I'm not sure if I totally "get" this sentence, but if I do, adding a comma after 
"characters" (the first occurence of it) would make it more clear or 
readable, IMHO. 
This would lead to: 
"Previously, there were only 256 possible ordinals for script characters, and 
texts were typically bound to a code page which mapped the ordinals to 
script characters." 
Just a thought. 

Logged In: YES 
user_id=313612

URL: http://docs.python.org/tut/node5.html 
Part: 3.1.3 Unicode Strings 
Sentence: The small "u" in front of the quote indicates that an Unicode 
string is supposed to be created. 
 
Isn't it "a Unicode", instead of "an Unicode"? I wasn't too sure of this one, 
but Googling for both brings up much more results for "a Unicode", and, 
more importantly, the results are from more "official" entities (like 
unicode.org, for example). 

Logged In: YES 
user_id=469548

I checked in fixes for the problems you reported:

1. Fixed as you suggested.
2. Fixed as you suggested.
3. Split up the two into separate sentences.
4. It's "a Unicode" string. 'a' vs. 'an' is about
pronunciation (e.g.: an MRI). So, fixed as you suggested.

I'll close this bug now, but feel free to reopen it if you
find anymore problems with the tutorial.