merge aviflax-objects-not-hashes

gjtorikian · gjtorikian · commit b3f11ed3e385 · 2014-11-07T15:22:03.000-08:00
diff --git a/content/v3.md b/content/v3.md
@@ -133,7 +133,7 @@ receive request bodies:
         HTTP/1.1 400 Bad Request
         Content-Length: 40
 
-        {"message":"Body should be a JSON Hash"}
+        {"message":"Body should be a JSON object"}
 
 3. Sending invalid fields will result in a `422 Unprocessable Entity`
    response.
diff --git a/content/v3/gists.md b/content/v3/gists.md
@@ -68,11 +68,11 @@ Name | Type | Description
 
 Name | Type | Description
 -----|------|--------------
-`files`|`hash` | **Required**. Files that make up this gist.
+`files`|`object` | **Required**. Files that make up this gist.
 `description`|`string` | A description of the gist.
 `public`|`boolean` | Indicates whether the gist is public. Default: `false`
 
-The keys in the `files` hash are the `string` filename, and the value is another `hash` with a key of `content`, and a value of the file contents. For example:
+The keys in the `files` object are the `string` filename, and the value is another `object` with a key of `content`, and a value of the file contents. For example:
 
 <%= json \
   :description => "the description for this gist",
@@ -102,11 +102,11 @@ The keys in the `files` hash are the `string` filename, and the value is another
 Name | Type | Description
 -----|------|--------------
 `description`|`string` | A description of the gist.
-`files`|`hash` | Files that make up this gist.
+`files`|`object` | Files that make up this gist.
 `content`|`string` | Updated file contents.
 `filename`|`string` | New name for this file.
 
-The keys in the `files` hash are the `string` filename. The value is another `hash` with a key of `content` (indicating the new contents), or `filename` (indicating the new filename). For example:
+The keys in the `files` object are the `string` filename. The value is another `object` with a key of `content` (indicating the new contents), or `filename` (indicating the new filename). For example:
 
 <%= json \
   :description => "the description for this gist",
diff --git a/content/v3/rate_limit.md b/content/v3/rate_limit.md
@@ -36,16 +36,16 @@ Note: Accessing this endpoint does not count against your rate limit.
 The Search API has a [custom rate limit](/v3/search/#rate-limit), separate from
 the rate limit governing the rest of the API. For that reason, the response
 (shown above) categorizes your rate limit by resource. Within the `"resources"`
-hash, the `"search"` hash provides your rate limit status for the
-[Search API](/v3/search). The `"core"` hash provides your rate limit status for
+object, the `"search"` object provides your rate limit status for the
+[Search API](/v3/search). The `"core"` object provides your rate limit status for
 all the _rest_ of the API.
 
 #### Deprecation Notice
 
-The `"rate"` hash (shown at the bottom of the response above) is
+The `"rate"` object (shown at the bottom of the response above) is
 [deprecated](/v3/versions/#v3-deprecations) and is scheduled for removal in the next
 version of the API.
 
 If you're writing new API client code (or updating your existing code), you
-should use the `"core"` hash instead of the `"rate"` hash. The `"core"` hash
-contains the same information that is present in the `"rate"` hash.
+should use the `"core"` object instead of the `"rate"` object. The `"core"` object
+contains the same information that is present in the `"rate"` object.
