Merge pull request #3264 from btriller/some-fixes

Fix some format issues

examples/tutorials/installing-cfengine-enterprise-agent.markdown

@@ -14,6 +14,7 @@ This is the full version of CFEngine Enterprise host, but the number of hosts is
 **System requirements**
 
 CFEngine Hosts (clients)
+
 * 32/64-bit machines with a recent version of Linux
 * 20 mb of memory
 * 20mb of disk space

reference/language-concepts/augments.markdown

@@ -58,6 +58,7 @@ There are two canonical augments files, `host_specific.json`, and `def.json` whi
 as specified by the [_augments_ key][Augments#augments].
 
 **Notes:**
+
 * CFEngine variables are **not** expanded unless otherwise noted.
 
 ### host_specific.json
@@ -409,13 +410,13 @@ results in
   class `MISSING` is not defined.
 
 * `augments_class_from_single_class_as_regex` will be defined because the class
-  `cfengine` is always defined.
+  ```cfengine``` is always defined.
 
 * `augments_class_from_single_class_as_expression` will be defined because
-  `cfengine` is defined when interpreted as a class expression.
+  ```cfengine``` is defined when interpreted as a class expression.
 
 * `augments_class_from_classexpression_and` will be defined because the class
-  `cfengine` and the class `cfengine_3` are defined and the class expression
+  ```cfengine``` and the class `cfengine_3` are defined and the class expression
   `cfengine.cfengine_3::` evaluates to true.
 
 * `augments_class_from_classexpression_not` will be defined because the class
@@ -424,18 +425,18 @@ results in
 
 * `augments_class_from_classexpression_or` will be defined because the class
   expression `cfengine|cfengine_3::` evaluates to true since at least one of
-  `cfengine` or `cfengine_3` will always be defined by cfengine 3 agents.
+  ```cfengine``` or `cfengine_3` will always be defined by cfengine 3 agents.
 
 * `augments_class_from_classexpression_complex` will be defined because the
   class expression `(cfengine|cfengine_3).!MISSING::` evaluates to true since at
-  least one of `cfengine` or `cfengine_3` will always be defined by cfengine 3
+  least one of ```cfengine``` or `cfengine_3` will always be defined by cfengine 3
   agents and `MISSING` is not defined.
 
 * `myclass_defined_by_augments_in_def_json_3_18_0_v0` will be defined because
   the class expression `cfengine|linux::` will always be true since there is
-  always a `cfengine` class defined.
+  always a ```cfengine``` class defined.
 
-* `myclass_defined_by_augments_in_def_json_3_18_0_v1` will be defined because the expression `cfengine.**` will match at least one defined class, `cfengine`
+* `myclass_defined_by_augments_in_def_json_3_18_0_v1` will be defined because the expression `cfengine.**` will match at least one defined class, ```cfengine```
 
 You can see the list of classes thus defined through `def.json` in the output
 of `cf-promises --show-classes` (see [Components][]). They

reference/language-concepts/namespaces.markdown

@@ -47,7 +47,7 @@ A common mistake is forgetting to specify `default:` when using bodies from the
 
 ## Variables
 
-Variables (except for Special variables) are assumed to be within the same scope
+Variables (except for [Special variables][Special variables]) are assumed to be within the same scope
 as the promiser but can also be referenced fully qualified with the namespace.
 
 [%CFEngine_include_example(namespace_variable_references.cf)%]

reference/macros.markdown

@@ -191,7 +191,8 @@ syntax validation, so any CFEngine binary that is not compiled with
 the feature support macro will be able to exclude syntax from
 possibly incompatible versions.
 
-Currently available features are :
+Currently available features are:
+
 * `xml`
 * `yaml`
 * `curl`

reference/promise-types/files.markdown

@@ -1453,7 +1453,7 @@ if the `create` attribute is explicitly used.
 
 **History:**
 
-* 3.20.0 Changed default from `false` to `true` for cases of full file management ( e.g. when `template_method` is `mustache`, `inline_mustache` or `cfengine`, or when the `content` or `copy_from` attributes are used ).
+* 3.20.0 Changed default from `false` to `true` for cases of full file management ( e.g. when `template_method` is `mustache`, `inline_mustache` or ```cfengine```, or when the `content` or `copy_from` attributes are used ).
 
 ### delete
 
@@ -3076,15 +3076,15 @@ state in Mustache.
 
 **Description:** The template type.
 
-By default `cfengine` requests the native CFEngine template
+By default ```cfengine``` requests the native CFEngine template
 implementation, but you can use `mustache` or `inline_mustache` as well.
 
 [%CFEngine_promise_attribute(cfengine)%]
 
 #### template_method cfengine
 
 The default native-CFEngine template format (selected when
-[template_method][files#template_method] is `cfengine` or unspecified) uses inline tags to
+[template_method][files#template_method] is ```cfengine``` or unspecified) uses inline tags to
 mark regions and classes. Each line represents an `insert_lines`
 promise, unless the promises are grouped into a block using: