doc: Improve syntax highlighting by using json instead of js

Author: bfanger

versions/1.2.md

@@ -136,15 +136,15 @@ If the [`type`](#dataTypeType) field is included it MUST NOT have the value `arr
 ##### 4.3.4.1 Object Examples
 
 For a primitive type:
-```js
+```json
 {
   "type": "string"
 }
 ```
 
 For a complex type (model):
 
-```js
+```json
 {
   "$ref": "Pet"
 }
@@ -174,7 +174,7 @@ Field Name | Type | Description
 
 #### 5.1.1 Object Example
 
-```js
+```json
 {
   "apiVersion": "1.0.0",
   "swaggerVersion": "1.2",
@@ -247,7 +247,7 @@ Field Name | Type | Description
 
 ##### 5.1.2.1 Object Example:
 
-```js
+```json
 {
     "path": "/pets",
     "description": "Operations about pets."
@@ -268,7 +268,7 @@ Field Name | Type | Description
 
 ##### 5.1.3.1 Object Example:
 
-```js
+```json
 {
   "title": "Swagger Sample App",
   "description": "This is a sample server Petstore server.",
@@ -300,7 +300,7 @@ Field Name | Type | Description
 <a name="authorizationsAuthorizationName"/>{Authorization Name} | [Authorization Object](#515-authorization-object) | A new authorization definition. The name given to the {Authorization Name} is a friendly name that should be used when referring to the authorization scheme. In many cases, the {Authorization Name} used is the same as its type, but it can be anything.
 
 ##### 5.1.4.1 Object Example:
-```js
+```json
 {
   "oauth2": {
     "type": "oauth2",
@@ -397,7 +397,7 @@ Field Name | Type | Description
 <a name="scope"/>description | `string` | *Recommended.* A short description of the scope.
 
 ##### 5.1.6.1 Object Example:
-```js
+```json
 {
   "scope": "email",
   "description": "Access to your email address"
@@ -415,7 +415,7 @@ Field Name | Type | Description
 <a name="grantTypesAuthorizationCode"/>authorization_code | [Authorization Code Object](#519-authorization-code-object) | The Authorization Code Grant flow definition.
 
 ##### 5.1.7.1 Object Example:
-```js
+```json
 {
   "implicit": {
     "loginEndpoint": {
@@ -446,7 +446,7 @@ Field Name | Type | Description
 <a name="implicitTokenName"/>tokenName | `string` | An optional alternative name to standard "access_token" OAuth2 parameter.
 
 ##### 5.1.8.1 Object Example:
-```js
+```json
 {
   "loginEndpoint": {
     "url": "http://petstore.swagger.wordnik.com/oauth/dialog"
@@ -464,7 +464,7 @@ Field Name | Type | Description
 <a name="acTokenEndpoint"/>tokenEndpoint | [Token Endpoint Object](#5112-token-endpoint-object) | **Required.** The token endpoint definition.
 
 ##### 5.1.9.1 Object Example:
-```js
+```json
 {
   "tokenRequestEndpoint": {
     "url": "http://petstore.swagger.wordnik.com/oauth/requestToken",
@@ -486,7 +486,7 @@ Field Name | Type | Description
 <a name="leUrl"/>url | `string` | **Required.** The URL of the authorization endpoint for the implicit grant flow. The value SHOULD be in a URL format.
 
 ##### 5.1.10.1 Object Example:
-```js
+```json
 {
   "url": "http://petstore.swagger.wordnik.com/oauth/dialog"
 }
@@ -502,7 +502,7 @@ Field Name | Type | Description
 <a name="treCliendSecretName"/>clientSecretName | `string` | An optional alternative name to the standard "client_secret" OAuth2 parameter.
 
 ##### 5.1.11.1 Object Example:
-```js
+```json
 {
   "url": "http://petstore.swagger.wordnik.com/oauth/requestToken",
   "clientIdName": "client_id",
@@ -519,7 +519,7 @@ Field Name | Type | Description
 <a name="treTokenName"/>tokenName | `string` | An optional alternative name to standard "access_token" OAuth2 parameter.
 
 ##### 5.1.12.1 Object Example:
-```js
+```json
 {
   "url": "http://petstore.swagger.wordnik.com/oauth/token",
   "tokenName": "access_code"
@@ -543,7 +543,7 @@ Field Name | Type | Description
 <a name="adAuthorizations"/>authorizations | [Authorizations Object](#5210-authorizations-object) | A list of authorizations schemes *required* for the operations listed in this API declaration. Individual operations may override this setting. If there are multiple authorization schemes described here, it means they're **all** applied.
 
 #### 5.2.1 Object Example
-```js
+```json
 {
   "apiVersion": "1.0.0",
   "swaggerVersion": "1.2",
@@ -702,7 +702,7 @@ Field Name | Type | Description
 
 ##### 5.2.2.1 Object Example:
 
-```js
+```json
       {
       "path": "/pet",
       "operations": [
@@ -799,7 +799,7 @@ Field Name | Type | Description
 
 ##### 5.2.3.1 Object Example
 
-````js
+````json
         {
           "method": "GET",
           "summary": "Find pet by ID",
@@ -869,7 +869,7 @@ Field Name | Type | Description
 
 ##### 5.2.4.2 Object Example
 
-```js
+```json
 {
   "name": "body",
   "description": "Pet object that needs to be updated in the store",
@@ -891,7 +891,7 @@ Field Name | Type | Description |
 
 ##### 5.2.5.1 Object Example
 
-```js
+```json
   {
     "code": 404,
     "message": "no project found",
@@ -919,7 +919,7 @@ Field Name | Type | Description
 
 ##### 5.2.6.1 Object Example
 
-```js
+```json
 {
     "Category": {
       "id": "Category",
@@ -953,7 +953,7 @@ Field Name | Type | Description
 
 ##### 5.2.7.1 Object Example
 
-```js
+```json
 {
   "id": "Order",
   "properties": {
@@ -1040,7 +1040,7 @@ Field Name | Type | Description
 <a name="propertiesPropertyName"/>{Property Name} | [Property Object](#529-property-object) | A new model property definition. Note the actual name of the field is the name you're giving your property. For example, "id", "name", "age".
 
 ##### 5.2.8.1 Object Example
-```js
+```json
       {
         "id": {
           "type": "integer",
@@ -1116,7 +1116,7 @@ Field Name | Type | Description
 <a name="adAuthorizationsAuthorizationName"/>{Authorization Name} | * | The authorization scheme to be used. The name given to the {Authorization Name} MUST be a friendly name that was given to an authorization scheme in the Resource Listing's [authorizations](#rlAuthorizations). If the friendly name describes an OAuth2 security scheme, the value should be of type \[[Scope Object](#5211-scope-object)\] (but may be an empty array to denote 'no scopes'). For all other authorization scheme types, the value MUST be an empty array.
 
 ##### 5.2.10 Object Example:
-```js
+```json
 {
   "oauth2": [
     {
@@ -1140,7 +1140,7 @@ Field Name | Type | Description
 <a name="scope"/>description | `string` | *Recommended.* A short description of the scope.
 
 ##### 5.2.11.1 Object Example:
-```js
+```json
 {
   "scope": "email",
   "description": "Access to your email address"