Documentation fixes

[Ramiro Morales]

A few issues thata haven't already been reported in other Component:Documentation tickets: reST fixes, addition of Pygmentation to some files, typos.

[Adrian Holovaty]

Note that this patch did not apply cleanly for me, as it refers to "a/docs" and "b/docs". In the future, could you do a "svn diff" from within the main "trunk" directory to produce a clean patch?

[Adrian Holovaty]

(In [8987]) Fixed #8979 -- Made a bunch of typo/formatting fixes to the docs. Thanks, ramiro

[Ramiro Morales]

Replying to adrian:

Note that this patch did not apply cleanly for me, as it refers to "a/docs" and "b/docs". In the future, could you do a "svn diff" from within the main "trunk" directory to produce a clean patch?

Problem is I don't use SVN, the patch was generated from work in a named branch in a Mercurial repository, I think git does also generates that kind of patches. See Jacob's comment ​here

[Marc Fargas]

Replying to adrian:

Note that this patch did not apply cleanly for me, as it refers to "a/docs" and "b/docs". In the future, could you do a "svn diff" from within the main "trunk" directory to produce a clean patch?

Tip: "patch -p1 < diff-file.diff"

The "-pN" parameter means "Strip the smallest prefix containing num leading slashes...", so, in this case would mean "Strip b/ and a/". It defaults to "-p0" ;)

Git, Mercurial, even doing diff by hand (i.e. when using a release tarball) will generate diff with those prefix, then "-p1" does the job ;)

[Adrian Holovaty]

Looks like I missed the Cool Kids' memo about Git patches. Thanks for the pointer!