fix markup

Author: gfldex

doc/Language/grammar_tutorial.pod6

@@ -78,10 +78,10 @@ As you can see above, in TOP, the "<thingy>" token is mentioned. The <thingy> is
 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:
 
 
-    =item1 # The first part of the URI we'll call the "subject", like a part, or a product, or a person.
-    =item1 # The second part of the URI we'll call the "command", like standard CRUD stuff (create, retrieve, update, or delete).
-    =item1 # The third part of the URI will be arbitrary data. Perhaps the specific ID we'll be working with, or a long list of data separated by "/"'s.
-    =item1 # When we get a URL, we'll want 1-3 above to be placed into a nice data structure we can use without having to do all sorts of splitting, and that can be easily altered in the future or expanded upon (or extended).
+    =item1 The first part of the URI we'll call the "subject", like a part, or a product, or a person.
+    =item1 The second part of the URI we'll call the "command", like standard CRUD stuff (create, retrieve, update, or delete).
+    =item1 The third part of the URI will be arbitrary data. Perhaps the specific ID we'll be working with, or a long list of data separated by "/"'s.
+    =item1 When we get a URL, we'll want 1-3 above to be placed into a nice data structure we can use without having to do all sorts of splitting, and that can be easily altered in the future or expanded upon (or extended).
 
 So if we got a URI on the server of "/product/update/7/notify" we would want our grammar to give us a nice $match object that has a "I<subject>" of "product", a "I<command>" of "update" and "I<data>" of "7/notify" (for now).