Review feedback (formatting, typos, etc.)

Co-authored-by: Ralf Handl <[email protected]>

Author: handrews

versions/3.0.4.md

@@ -2074,13 +2074,13 @@ for specifications with external references.
 
 Keys and values for `parameters` have multiple syntaxes:
 
-* The key can either be just the parameter name, or can be qualified using the [parameter location](#parameterIn) `[{in}.]{name}` for operations that use the same parameter name in different locations (e.g. path\.id).
-* The value can be a literal value or a [Runtime Expression](#runtimeExpression)
+* The key can either be just the parameter name, or can be qualified using the [parameter location](#parameterIn) `[{in}.]{name}` for operations that use the same parameter name in different locations (e.g. `path.id`).
+* The value can be a literal value or a [Runtime Expression](#runtimeExpression).
 
 Certain keys and values for `parameters` can be ambiguous, in which case their handling is implementation-defined as it was not spelled out in earlier versions of OAS 3.0.  However, it is RECOMMENDED that: 
 
-* Keys that match unqualified parameter names be treated as those names, as a parameter that is (confusingly) named to appear qualified (e.g. `path\.id`) can be qualified to disambiguate it (e.g. `path\.path\.id`)
-* Values that are valid runtime expressions be handled as runtime expressions, although this means that it is not possible to pass a literal value that looks like a runtime expression
+* Keys that match unqualified parameter names be treated as those names, as a parameter that is (confusingly) named to appear qualified (e.g. `path.id`) can be qualified to disambiguate it (e.g. `path.path.id`).
+* Values that are valid runtime expressions be handled as runtime expressions, although this means that it is not possible to pass a literal value that looks like a runtime expression.
 
 ##### Examples