Minor edits for typos in documentation.

Author: woodbri

DOCUMENTATION.md

@@ -28,6 +28,9 @@ key component that can help in that task. Additionally, if you need to change
 the underlying data that is being matched for example by adding a new
 country to the standardizer or adding an new reference set, then this document
 will help explain the how it works and what you can do to make those changes.
+If you work with PostgreSQl database this provides and extension to the database
+and SQl wrappers for accessing this code. Alternatively for developer you can
+link this code directly into your C/C++ application and access it from there.
 
 ## How Does It Work?
 
@@ -627,4 +630,12 @@ global changes (ie: ones related to may addresses or a class of addresses)
 making adjustments to the grammar is better. I typically look at 1,000s if not
 1,000,000s of records when building a new Lexicon and Grammar.
 
+## See Also
+
+* [Overview](docs/overview.md)
+* [Token](docs/token.md)
+* [Lexicon](docs/lexicon.md)
+* [Grammar](docs/grammar.md)
+* [InClass::Type](docs/inclass.md)
+* [OutClass::Type](docs/outclass.md)
 

docs/grammar.md

@@ -22,10 +22,10 @@ need to account for things like optional fields, maybe apartment numbers, etc.
 
 The first example might match many addresses in the US and Canada. The USPS has
 a document Pub. 28 that defines valid address structure and acceptable
-abbreviations the can be used to build the Lexicon.
+abbreviations that can be used to build the Lexicon.
 
 The second example might be used at the top level to match some European
-country addresses where the house number follows the streat name.
+country addresses where the house number follows the street name.
 
 The third example might be used by someone that is only working with a small
 subset of data covering a single city where there is no need to differentiate
@@ -59,7 +59,7 @@ tokens.
 The second example ``[house_number]`` has a different format and here we have
 to consume input tokens, ie: the tokens before the first '->'.
 
-The ``[ADDRESS]`` style section is referred to a *MetaSection* and the
+The ``[ADDRESS]`` style section is referred to as a *MetaSection* and the
 ``[house_number]`` section is referred to as a *RuleSection*. You can not mix
 *MetaSection* lines with *RuleSection* lines. In the *MetaSection* in the
 grammar file all references are preceded by an '@' character, so the example

docs/inclass.md

@@ -62,7 +62,7 @@ The list of input types is:
 | ATT_PRE   |  Attached prefix |
 | ATT_SUF   |  Attached suffix |
 
-You can use *DETACHED* or leave the field empty to indicate that the the token is not attached. *DET_PRE*, *DET_SUF*, *ATT_PRE*, *ATT_SUF* can be placed in a comma separated list ass appropriate to indicate the possible attachments for the token. For example *STRASSE* could have *DET_SUF,ATT_SUF* associated with it to indcate that it follows the street name and might be attached or not.
+You can use *DETACHED* or leave the field empty to indicate that the the token is not attached. *DET_PRE*, *DET_SUF*, *ATT_PRE*, *ATT_SUF* can be placed in a comma separated list as appropriate to indicate the possible attachments for the token. For example *STRASSE* could have *DET_SUF,ATT_SUF* associated with it to indcate that it follows the street name and might be attached or not.
 
 
 ## See Also

docs/outclass.md

@@ -18,7 +18,7 @@ The full list of OutClass types is listed in the following table.
 | ------------- | ----------- |
 | BLDNG   | Unparsed building identifiers and types. |
 | HOUSE   | The civic address number. The '123' in '123 MAIN ST' |
-| PREDIR  | A directional modifier that precedes the street name. Example, the 'WEST' in '3715 TENTH AVENUE WEST'. |
+| PREDIR  | A directional modifier that precedes the street name. Example, the 'WEST' in '3715 WEST TENTH AVENUE'. |
 | QUALIF  | A pre or post modifier. Example, the 'OLD' in '3715 OLD HIGHWAY 99' or 'BUSINESS' in '1203 HIGHWAY 45 BUSINESS'. |
 | PRETYP  | A street type preceding the root street name. Example, the 'HIGHWAY' in '3715 HIGHWAY 99'. |
 | STREET  | The root street name, stripped of directional or type modifiers. Example, the 'TENTH' in '3715 WEST TENTH AVENUE'. |

docs/token.md

@@ -11,7 +11,7 @@ example, *ST* can be classified as *TYPE* in the context of *STREET* or as
 against the grammar are we able to determine which context is most likely to be
 the context of usage for this particular address.
 
-The Token object as the following fields:
+The Token object has the following fields:
 
 * WORD - a word or phrase parsed from the address string
 * STDWORD - a standardized version of *WORD* based on the Lexicon or *WORD*