On page 4, under What Plugins do, Objective C is generally referenced as Objective-C Yeah, it's a nit, but it's how it show's up in Google!

On page 5, step #3, it should be [its supporting database] instead of [it's supporting database]. (Using brackets instead of quotes here)

On page 6, it should be [/files/plugins directory] instead of [/files plugins directory]. Missing a slash.

Found a few more here too, figured I would give it an hour or so ;-)

On page 8, should be [plugin its based] and not [plugin it's based].

Starting on page 9, I think it should be 'source code' and not 'source-code'.

Page 10, near the top, should read [files in its directory] and not [files in it's directory]. It's is a contraction of it and is, so it doesn't make much sense!

Bottom of page 10, [its information] vs [it's information].

Middle of page 11, Objective-C vs Objective C.

Page 13, [Updating a plugin after its been distributed] vs. [Updating a plugin after it's been distributed]. Gotta hate those contractions sometimes!

I've only gone through the Table of Contents, but here are some things I've noticed: The style for plugins should also be consistently lowercase, unless you're using it in a heading. For instance, in the Table of Contents, you use plugins for most of the chapter subcategories, but Plugins for those in the Managing... chapter: About Plugins............................................................................................ 3 UPPERCASE Plugins OK HERE, SINCE IT'S A CHAPTER HEADER Why plugins are necessary....................................................................... 3 LOWERCASE plugins OK HERE What plugins do......................................................................................4 LOWERCASE plugins OK HERE Who creates plugins................................................................................ 4 LOWERCASE plugins OK HERE How do I get new plugins.........................................................................4 LOWERCASE plugins OK HERE Managing Plugins in the Control Panel...........................................................4 UPPERCASE Plugins OK HERE, SINCE IT'S A CHAPTER HEADER Installing Plugins.....................................................................................5 SHOULD BE LOWERCASE plugins HERE Updating Plugins.....................................................................................5 SHOULD BE LOWERCASE plugins HERE Removing Plugins....................................................................................6 SHOULD BE LOWERCASE plugins HERE Plugins on the web server........................................................................6 UPPERCASE Plugins OK HERE, SINCE IT'S THE FIRST WORD Also, in that last line above, the period to the left of 6 (page number) is crashing into the number. Needs an extra space or two. Modifying a screens behavior > should be Modifying a screen's behavior (in both the Table of Contents and on Page 8) Updating a plugin after its been distributed > should be Updating a plugin after it has been distributed (in both the Table of Contents and on Page 13) The same rules of consistency should be applied to the use of Plugins and plugins throughout the document. Also, you need to add page numbers to the PDF :-)

@manga_university - Modifying a screens behavior > should be Modifying a screen's behavior (in both the Table of Contents and on Page 8) - Is that right? P5 The steps to updating a plugin are identical to the <step> to install a plugin The steps to updating a plugin are identical to the <steps> to install a plugin P7 (very picky!) When you click the ''Refresh Plugins'' link in the control panel, the software inspects the <contents> of each of the folders When you click the ''Refresh Plugins'' link in the control panel, the software inspects the <content> of each of the folders P7 The number of properties and the types of information required to make a plugin work <is> determined The number of properties and the types of information required to make a plugin work <are> determined P8 When you add a new screen to an application, <it's> default When you add a new screen to an application, <its> default P9 There <> a few things to think about There <are> a few things to think about P11 <It's> purpose is to explain in plain-language how the plugin works, what <it's> purpose is <Its> purpose is to explain in plain-language how the plugin works, what <its> purpose is P11 Additional files in this <filer> may be graphics Additional files in this <folder> may be graphics P11 images around 396 x 744 <wish> is appropriate images around 396 x 744 <which> is appropriate P12 Change the display <as> to: Empty Screen Change the display <> to: Empty Screen

@raveyd — Yes, it should be screen's, with an apostrophe, since the word is used as a possessive (i.e. Modifying the behavior of a screen), In fact, that may be the best way to phrase the TOC entry: Modifying the behavior of a screen.

Loving the English majors! Good stuff. On it.