STYLE: Tune description of code fence example
MODIFY
STYLE.md
STYLE.md
@@ -187,7 +187,7 @@ quay.io/coreosinc/coreos-pages-builder scripts/deploy stage
### Example: Documenting code blocks
-To format a code block in a document, insert triple backticks ` ``` ` ` ``` ` on a new line before and after the code block. A tag, such as `yaml`, `sh`, `json`, or `ini`, can be placed after the opening backticks to declare the language in the block.
+Insert triple backtick (grave accent) characters on a new line before and after a block of code. A tag, such as `yaml`, `sh`, `json`, or `ini`, can be placed after the opening backticks to declare the language in the block. Markdown syntax is not interpreted within the gated code block, but special characters are replaced with HTML entities.
```yaml
apiVersion: v1
@@ -204,6 +204,9 @@ spec:
app: etcd
```
+View this document's source to see the Markdown that generates the code block above.
+
+
## File name extension conventions
Some file types are commonly identified with more than one file name extension. For example, YAML is usually stored in files whose names end in either `.yml`, or `.yaml`. For the sake of consistency, use the file name extension designated in the following list when referring to or creating files of any of the listed types in CoreOS projects and their documentation.

STYLE: Tune description of code fence example