Re: Typos in Developer's Reference

2017-09-16 Thread Sean Whitton
Hello Paul, On Sat, Sep 16 2017, Paul Hardy wrote: > I was educated by some pretty old-fashioned American English teachers when > I was a kid, but I have moved away from a lot of what they taught me. I > wouldn't recommend any change to make a document sound more stodgy or > anachronistic. Stil

Re: Typos in Developer's Reference

2017-09-16 Thread Paul Hardy
On Wed, Sep 13, 2017 at 10:34 AM, Sean Whitton wrote: > On Sun, Sep 10 2017, Paul Hardy wrote: > >> 1) There are instances where "i.e." and "e.g." have commas after them, >> and instances where they do not. If you have a preference for one >> over the other, I can mark the document so it is consi

Re: Typos in Developer's Reference

2017-09-13 Thread Sean Whitton
On Sun, Sep 10 2017, Paul Hardy wrote: > 1) There are instances where "i.e." and "e.g." have commas after them, > and instances where they do not. If you have a preference for one > over the other, I can mark the document so it is consistent. If > nobody has a preference, I will just put commas

Typos in Developer's Reference

2017-09-10 Thread Paul Hardy
Dear Developer's Reference Maintainers, I took a PDF copy of the Developer's Reference manual with me recently while on travel. I marked a number of typos as I went through the document. I can submit a wishlist bug against developers-reference with patches after going through the sources, but fi