a few more cleanups to docs

docs/content/Tutorial:-A-First-Look-at-Druid.md

@@ -289,7 +289,7 @@ and put the following in there:
   "dataSource": "wikipedia", 
   "granularity": "all", 
   "dimensions": [ "page" ], 
-  "orderBy": {
+  "limitSpec": {
      "type": "default", 
      "columns": [ { "dimension": "edit_count", "direction": "DESCENDING" } ], 
      "limit": 10

docs/content/Tutorial:-Webstream.md

@@ -251,7 +251,7 @@ and put the following in there:
     "dataSource": "webstream", 
     "granularity": "all", 
     "dimensions": [ "geo_region" ], 
-    "orderBy": {
+    "limitSpec": {
         "type": "default", 
         "columns": [
             { "dimension": "known_users",  "direction": "DESCENDING" }

docs/content/Twitter-Tutorial.md

@@ -306,7 +306,7 @@ and put the following in there:
     "dataSource": "twitterstream",
     "granularity": "all",
     "dimensions": ["htags"],
-    "orderBy": {"type":"default", "columns":[{"dimension": "tweets", "direction":"DESCENDING"}], "limit":5},
+    "limitSpec": {"type":"default", "columns":[{"dimension": "tweets", "direction":"DESCENDING"}], "limit":5},
     "aggregations":[
       { "type": "longSum", "fieldName": "tweets", "name": "tweets"}
     ],
@@ -315,7 +315,7 @@ and put the following in there:
 }
 ```
 
-Woah! Our query just got a way more complicated. Now we have these "Filters":Filters.html things and this "LimitSpec":LimitSpec.html thing. Fear not, it turns out the new objects we've introduced to our query can help define the format of our results and provide an answer to our question.
+Woah! Our query just got a way more complicated. Now we have these [Filters](Filters.html) things and this [LimitSpec](LimitSpec.html) thing. Fear not, it turns out the new objects we've introduced to our query can help define the format of our results and provide an answer to our question.
 
 If you issue the query: