Fewer commas, formatting, ABNF indentation

Author: ralfhandl

versions/3.0.4.md

@@ -2285,7 +2285,7 @@ The presence of a link does not guarantee the caller's ability to successfully i
 
 Unlike _dynamic_ links (i.e. links provided **in** the response payload), the OAS linking mechanism does not require link information in the runtime response.
 
-For computing links, and providing instructions to execute them, a [runtime expression](#runtime-expressions) is used for accessing values in an operation and using them as parameters while invoking the linked operation.
+For computing links and providing instructions to execute them, a [runtime expression](#runtime-expressions) is used for accessing values in an operation and using them as parameters while invoking the linked operation.
 
 ##### Fixed Fields
 
@@ -2372,10 +2372,10 @@ links:
 ```
 
 Clients follow all links at their discretion.
-Neither permissions, nor the capability to make a successful call to that link, is guaranteed
+Neither permissions nor the capability to make a successful call to that link is guaranteed
 solely by the existence of a relationship.
 
-##### OperationRef Examples
+##### `operationRef` Examples
 
 As references to `operationId` MAY NOT be possible (the `operationId` is an optional
 field in an [Operation Object](#operation-object)), references MAY also be made through a relative `operationRef`:
@@ -2400,8 +2400,8 @@ links:
       username: $response.body#/username
 ```
 
-Note that in the use of `operationRef`, the _escaped forward-slash_ is necessary when
-using JSON Pointer, and it is necessary to URL-encode `{` and `}` as `%7B` and `%7D`, respectively when using JSON Pointer as URI fragments.
+Note that in the use of `operationRef` the _escaped forward-slash_ is necessary when
+using JSON Pointer, and it is necessary to URL-encode `{` and `}` as `%7B` and `%7D`, respectively, when using JSON Pointer as URI fragments.
 
 ##### Runtime Expressions
 
@@ -2411,22 +2411,22 @@ This mechanism is used by [Link Objects](#link-object) and [Callback Objects](#c
 The runtime expression is defined by the following [ABNF](https://tools.ietf.org/html/rfc5234) syntax
 
 ```abnf
-    expression = ( "$url" / "$method" / "$statusCode" / "$request." source / "$response." source )
-    source = ( header-reference / query-reference / path-reference / body-reference )
+    expression = "$url" / "$method" / "$statusCode" / "$request." source / "$response." source
+    source     = header-reference / query-reference / path-reference / body-reference
     header-reference = "header." token
-    query-reference = "query." name
-    path-reference = "path." name
-    body-reference = "body" ["#" json-pointer ]
+    query-reference  = "query." name
+    path-reference   = "path." name
+    body-reference   = "body" ["#" json-pointer ]
     json-pointer    = *( "/" reference-token )
     reference-token = *( unescaped / escaped )
     unescaped       = %x00-2E / %x30-7D / %x7F-10FFFF
-       ; %x2F ('/') and %x7E ('~') are excluded from 'unescaped'
+                    ; %x2F ('/') and %x7E ('~') are excluded from 'unescaped'
     escaped         = "~" ( "0" / "1" )
-      ; representing '~' and '/', respectively
+                    ; representing '~' and '/', respectively
     name = *( CHAR )
     token = 1*tchar
-    tchar = "!" / "#" / "$" / "%" / "&" / "'" / "*" / "+" / "-" / "." /
-      "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
+    tchar = "!" / "#" / "$" / "%" / "&" / "'" / "*" / "+" / "-" / "."
+          / "^" / "_" / "`" / "|" / "~" / DIGIT / ALPHA
 ```
 
 Here, `json-pointer` is taken from [RFC6901](https://tools.ietf.org/html/rfc6901), `char` from [RFC7159](https://tools.ietf.org/html/rfc7159#section-7) and `token` from [RFC7230](https://tools.ietf.org/html/rfc7230#section-3.2.6).