Docs: Fix minor formatting/grammar errors (#12371)

* Docs: Fix link to code conventions

* Docs: Fix formattting

* Docs: Fix formatting of example config

All other example configs in the docs spaced curly braces in object literals, so this commit updates this for consistency.

* Docs: Fixed grammar

* Docs: Revert link to code conventions

This reverts commit ab5dba7.

* Docs: Revert link to code conventions

* Docs: Revert link to code conventions

Sorry for all the commits.

Author: cherryblossom000

docs/rules/no-obj-calls.md

@@ -12,7 +12,7 @@ The [ECMAScript 2015 specification](https://www.ecma-international.org/ecma-262/
 
 And the [ECMAScript 2017 specification](https://www.ecma-international.org/ecma-262/8.0/index.html#sec-atomics-object) makes it clear that `Atomics` cannot be invoked:
 
-> The Atomics object does not have a [[Call]] internal method; it is not possible to invoke the Atomics object as a function.
+> The Atomics object does not have a `[[Call]]` internal method; it is not possible to invoke the Atomics object as a function.
 
 ## Rule Details
 

docs/rules/space-infix-ops.md

@@ -23,7 +23,7 @@ This rule is aimed at ensuring there are spaces around infix operators.
 This rule accepts a single options argument with the following defaults:
 
 ```json
-"space-infix-ops": ["error", {"int32Hint": false}]
+"space-infix-ops": ["error", { "int32Hint": false }]
 ```
 
 ### `int32Hint`

docs/rules/symbol-description.md

@@ -1,6 +1,6 @@
 # require symbol description (symbol-description)
 
-The `Symbol` function may have optional description:
+The `Symbol` function may have an optional description:
 
 ```js
 var foo = Symbol("some description");