Fix some minor issues

* Remove some trailing garbage
* Add and update some formatting
* Fix title for is_type()

Author: btriller

getting-started/installation/general-installation/installation-community.markdown

@@ -76,19 +76,19 @@ sudo rpm -i cfengine-community-{{site.cfengine.branch}}.{{site.cfengine.latest_p
 **Newer 64-bit DEB based distributions: (Ubuntu/Debian)**
 
 ```command
-sudo dpkg -i cfengine-community_{{site.cfengine.branch}}.{{site.cfengine.latest_patch_release}}-{{site.cfengine.latest_package_build}}_amd64-debian7.deb`
+sudo dpkg -i cfengine-community_{{site.cfengine.branch}}.{{site.cfengine.latest_patch_release}}-{{site.cfengine.latest_package_build}}_amd64-debian7.deb
 ```
 
 **Older 64-bit DEB based distributions: (Ubuntu/Debian)** (not recommended for policy server)
 
 ```command
-sudo dpkg -i cfengine-community_{{site.cfengine.branch}}.{{site.cfengine.latest_patch_release}}-{{site.cfengine.latest_package_build}}_amd64-debian4.deb`
+sudo dpkg -i cfengine-community_{{site.cfengine.branch}}.{{site.cfengine.latest_patch_release}}-{{site.cfengine.latest_package_build}}_amd64-debian4.deb
 ```
 
 **32-bit DEB based distributions: (Ubuntu/Debian)** (not recommended for policy server)
 
 ```command
-sudo dpkg -i cfengine-community_{{site.cfengine.branch}}.{{site.cfengine.latest_patch_release}}-{{site.cfengine.latest_package_build}}_i386-debian4.deb`
+sudo dpkg -i cfengine-community_{{site.cfengine.branch}}.{{site.cfengine.latest_patch_release}}-{{site.cfengine.latest_package_build}}_i386-debian4.deb
 ```
 
 **Note:** You might get a message like this: "Policy is not found in /var/cfengine/inputs, not starting CFEngine." Do not worry;
@@ -105,7 +105,11 @@ Run the bootstrap command:
 sudo /var/cfengine/bin/cf-agent --bootstrap <IP address of policy server>
 ```
 
-**Example: $ sudo /var/cfengine/bin/cf-agent --bootstrap 192.168.1.12**
+**Example:**
+
+```command
+sudo /var/cfengine/bin/cf-agent --bootstrap 192.168.1.12
+```
 
 Upon successful completion, a confirmation message appears: "Bootstrap to '192.168.1.12' completed successfully!"
 
@@ -132,6 +136,10 @@ the Policy Server. Run the same commands that you ran in Step 3.
 sudo /var/cfengine/bin/cf-agent --bootstrap <IP address of policy server>
 ```
 
-**Example: $ sudo /var/cfengine/bin/cf-agent --bootstrap 192.168.1.12**
+**Example:**
+
+```command
+sudo /var/cfengine/bin/cf-agent --bootstrap 192.168.1.12
+```
 
 The CFEngine installation process is complete.

reference/components/cf-monitord.markdown

@@ -13,12 +13,12 @@ available as [special variables][special variables] (e.g.
 [`$(mon.av_cpu)`][mon#mon.av_cpu]) to `cf-agent`, which may use them to inform
 policy decisions.
 
-`cf-monitord` keeps the promises made in `common`and `monitor` bundles, and is
-affected by  `common` and `monitor` control bodies.
+`cf-monitord` keeps the promises made in `common` and `monitor` bundles and is
+affected by `common` and `monitor` control bodies.
 
 **Notes:**
 
-* `cf-monitord` always considers the class ```monitor``` to be defined.
+* `cf-monitord` always considers the class `monitor` to be defined.
 
 ## Command reference
 
@@ -115,9 +115,9 @@ Slots with a higher number are used for custom measurement promises in
 CFEngine Enterprise.
 
 These values collected and analyzed by `cf-monitord` are transformed
-into agent variables in the `$(mon.`name`)` context.
+into agent variables in the `$(mon.name)` context.
 
-Note: There is no way for force a refresh of the monitored data.
+**Note:** There is no way for force a refresh of the monitored data.
 
 ## Data storage
 

reference/functions/accumulated.markdown

@@ -9,10 +9,10 @@ published: true
 **Description:** Convert an accumulated amount of time into a system representation.
 
 The `accumulated` function measures total accumulated runtime. Arguments
-are applied additively, so that accumulated(0,0,2,27,90,0) means "2
+are applied additively, so that `accumulated(0,0,2,27,90,0)` means "2
 days, 27 hours and 90 minutes of runtime" ". However, you are strongly
 encouraged to keep your usage of `accumulated` sensible and readable;
-for example, accumulated(0,0,0,48,0,0) or accumulated(0,0,0,0,90,0).
+for example, `accumulated(0,0,0,48,0,0)` or `accumulated(0,0,0,0,90,0)`.
 
 
 **Arguments:**
@@ -78,9 +78,4 @@ body process_count anyprocs
 In the example we look for processes that have accumulated between 2 and
 20 minutes of total run time.
 
-**See also:**
-
-* Related functions
-    * [`ago()`][ago]
-    * [`now()`][now]
-    * [`irange()`][irange]
+**See also:** `ago()`, `now()`, `irange()`

reference/functions/ago.markdown

@@ -9,10 +9,10 @@ published: true
 **Description:** Convert a time relative to now to an integer system representation.
 
 The `ago` function measures time relative to now. Arguments are applied
-in order, so that ago(0,18,55,27,0,0) means "18 months, 55 days, and 27
+in order, so that `ago(0,18,55,27,0,0)` means "18 months, 55 days, and 27
 hours ago". However, you are strongly encouraged to keep your usage of
-`ago` sensible and readable, e.g., ago(0,0,120,0,0,0) or
-ago(0,0,0,72,0,0).
+`ago` sensible and readable, e.g., `ago(0,0,120,0,0,0)` or
+`ago(0,0,0,72,0,0)`.
 
 **Arguments:**
 
@@ -50,9 +50,4 @@ Output:
 
 [%CFEngine_include_snippet(ago.cf, #\+begin_src\s+example_output\s*, .*end_src)%]
 
-**See also:**
-
-* Related functions
-    * [`now()`][now]
-    * [`accumulated()`][accumulated]
-    * [`irange()`][irange]
+**See also:** `now()`, `accumulated()`, `irange()`.

reference/functions/canonifyuniquely.markdown

@@ -10,7 +10,7 @@ published: true
 
 This function turns arbitrary text into class data, appending the
 SHA-1 hash for uniqueness.  It is exactly equivalent to
-`concat(canonify($(string)), "_", hash($(string),"sha1");` for a given
+`concat(canonify($(string)), "_", hash($(string),"sha1"));` for a given
 `$(string)` but is much more convenient to write and remember.
 
 A common use case is when you need unique array keys for each file in
@@ -30,4 +30,4 @@ commands:
        if => canonifyuniquely("start_$(component)");
 ```
 
-**See also:** [canonify()][canonify]).
+**See also:** `canonify()`.

reference/functions/data_expand.markdown

@@ -36,8 +36,6 @@ Output:
 
 [%CFEngine_include_snippet(data_expand.cf, #\+begin_src\s+example_output\s*, .*end_src)%]
 
-**Notes:**
-
 **History:** Was introduced in version 3.7.0 (2015). The [collecting functions][Functions#collecting functions] behavior was added in 3.9.
 
 **See also:** [`readcsv()`][readcsv], [`readjson()`][readjson], [`readyaml()`][readyaml], [`mergedata()`][mergedata], [`readenvfile()`][readenvfile], [`classfiltercsv()`][classfiltercsv], [about collecting functions][Functions#collecting functions], and `data` documentation.

reference/functions/dirname.markdown

@@ -21,9 +21,6 @@ Output:
 
 [%CFEngine_include_snippet(dirname.cf, #\+begin_src\s+example_output\s*, .*end_src)%]
 
-**Notes:**
-
 **History:** Was introduced in 3.3.0, Nova 2.2.0 (2011)
 
-**See also:** [`lastnode()`][lastnode], [`filestat()`][filestat],
-[`splitstring()`][splitstring].
+**See also:** `lastnode()`, `filestat()`, `splitstring()`.

reference/functions/execresult.markdown

@@ -17,7 +17,7 @@ CFEngine's control. Thus using a shell is both a performance hog and a
 potential security issue.
 
 The optional `output` argument allows you to select which output will be
-included, betweeen `stdout`, `stderr`, or `both`. The default is `both`.
+included, betweeen `stdout`, `stderr` or `both`. The default is `both`.
 
 [%CFEngine_function_attributes(command, shell, output)%]
 
@@ -46,7 +46,7 @@ highly undesirable if the command is expensive.  Consider using
 `commands` promises instead, which have locking and are not evaluated
 by `cf-promises`.
 
-**See also:** [`returnszero()`][returnszero], [`execresult_as_data()`][execresult_as_data].
+**See also:** `returnszero()`, `execresult_as_data()`.
 
 **History:**
 

reference/functions/findfiles.markdown

@@ -27,9 +27,6 @@ deep.
 This function, used together with the `bundlesmatching` function,
 allows you to do dynamic inputs and a dynamic bundle call chain.
 
-**History:**
-- Brace expression (i.e., `{foo,bar}`) and negative bracket expressions (i.e., `[!abc]`) were introduced in 3.24.
-
 **Example:**
 
 [%CFEngine_include_snippet(findfiles.cf, #\+begin_src cfengine3, .*end_src)%]
@@ -38,4 +35,8 @@ Output:
 
 [%CFEngine_include_snippet(findfiles.cf, #\+begin_src\s+example_output\s*, .*end_src)%]
 
-**See also:** [`bundlesmatching()`][bundlesmatching], [`findfiles_up()`][findfiles_up].
+**History:**
+
+- Brace expression (i.e., `{foo,bar}`) and negative bracket expressions (i.e., `[!abc]`) were introduced in 3.24.
+
+**See also:** `bundlesmatching()`, `findfiles_up()`.

reference/functions/findfiles_up.markdown

@@ -32,9 +32,6 @@ deep.
 * `[!a-z]` matches any letter not from `a` to `z`.
 * `{foo,bar}` matches `foo` or `bar`.
 
-**History:**
-- Brace expression (i.e., `{foo,bar}`) and negative bracket expressions (i.e., `[!abc]`) were introduced in 3.24.
-
 [%CFEngine_function_attributes(path, glob, level)%]
 
 **Example:**
@@ -45,6 +42,9 @@ Output:
 
 [%CFEngine_include_snippet(findfiles_up.cf, #\+begin_src\s+example_output\s*, .*end_src)%]
 
-**History:** Introduced in 3.18.
+**History:**
+
+- Introduced in 3.18.
+- Brace expression (i.e., `{foo,bar}`) and negative bracket expressions (i.e., `[!abc]`) were introduced in 3.24.
 
-**See also:** [`findfiles()`][findfiles].
+**See also:** `findfiles()`.