don't use 's for plurals

Author: coke

doc/Language/grammar_tutorial.pod6

@@ -75,7 +75,7 @@ As you can see above, in TOP, the "<thingy>" token is mentioned. The <thingy> is
 
 =head1 Learning By Example - a REST Contrivance
 
-Let's suppose we'd like to parse a URL into the component parts that make up a RESTful request. Let's decide that we want the URL's to work like this:
+Let's suppose we'd like to parse a URL into the component parts that make up a RESTful request. Let's decide that we want the URLs to work like this:
 
 
     =item1 The first part of the URI we'll call the "subject", like a part, or a product, or a person.
@@ -140,7 +140,7 @@ The REST grammar so far will handle retrieves, deletes and updates ok. However,
     # ｢product｣｢create｣
     =end code
 
-Let's imagine, for the sake of demonstration, that we might want to allow these same URI's to be entered in by a user from the terminal. In that case, they might put spaces between the '/'s, since users are prone to break things. If we wanted to accommodate this possibility, we could replace the '/'s in TOP with another token that allowed for spaces on either side of it.
+Let's imagine, for the sake of demonstration, that we might want to allow these same URIs to be entered in by a user from the terminal. In that case, they might put spaces between the '/'s, since users are prone to break things. If we wanted to accommodate this possibility, we could replace the '/'s in TOP with another token that allowed for spaces on either side of it.
 
     =begin code
     grammar REST {
@@ -217,7 +217,7 @@ This is what we've come up for processing our RESTful URIs so far:
     }
     =end code
 
-Let's look at various URI's and how they behave being passed through our grammar.
+Let's look at various URIs and how they behave being passed through our grammar.
 
     =begin code :skip-test
     my @uris = ['/product/update/7/notify',
@@ -234,7 +234,7 @@ Let's look at various URI's and how they behave being passed through our grammar
     # Sub: item Cmd: delete Dat: 4
     =end code
 
-So with just this part of a grammar, we're getting almost everything we need. Our URI's get efficiently parsed and we're given a nice little data structure for the variables we need to work with.
+So with just this part of a grammar, we're getting almost everything we need. Our URIs get efficiently parsed and we're given a nice little data structure for the variables we need to work with.
 
 But look at that first line returned -- the I<data> token is returning the entire end of the URI as just one string. We need to be able to work with that 7 there. And that 4! Well, the 4 is easy... But the 7 had the extra /notify on the end, to signal the system to notify someone that a product was updated (perhaps).