Merge pull request #3386 from btriller/functions-formatting

functions: Fix formatting for package*matching

Author: nickanderson

reference/functions/packagesmatching.markdown

@@ -46,10 +46,12 @@ some desired packages, and finally reports if they are installed.
 [%CFEngine_include_example(packagesmatching.cf)%]
 
 **Refresh rules:**
+
 * installed packages cache used by packagesmatching() is refreshed at the end of each agent run in accordance with constraints defined in the relevant package module body.
 * installed packages cache is refreshed after installing or removing a package.
 * installed packages cache is refreshed if no local cache exists.
-        This means a reliable way to force a refresh of CFEngine's internal package cache is to simply delete the local cache:
+
+This means a reliable way to force a refresh of CFEngine's internal package cache is to simply delete the local cache:
 
 ```cf3
 $(sys.statedir)/packages_installed_<package_module>.lmdb*
@@ -65,7 +67,6 @@ $(sys.statedir)/software_packages.csv
 **History:**
 
 * Introduced in CFEngine 3.6
-
 * Function started using `package_module` based data sources by default, even if
   there is no `package_inventory` attribute defined in `body common control` if
   available in 3.23.0

reference/functions/packageupdatesmatching.markdown

@@ -50,10 +50,12 @@ vars:
 ```
 
 **Refresh rules:**
+
 * updates cache used by packageupdatesmatching() is refreshed at the end of each agent run in accordance with constraints defined in the relevant package module body.
 * updates cache is refreshed every time `repo` type package is installed or removed
 * updates cache is refreshed if no local cache exists.
-        This means a reliable way to force a refresh of CFEngine's internal package cache is to simply delete the local cache:
+
+This means a reliable way to force a refresh of CFEngine's internal package cache is to simply delete the local cache:
 
 ```cf3
 $(sys.statedir)/packages_updates_<package_module>.lmdb*
@@ -68,7 +70,6 @@ $(sys.statedir)/software_patches_avail.csv
 **History:**
 
 * Introduced in CFEngine 3.6
-
 * Function started using `package_module` based data sources by default, even if
   there is no `package_inventory` attribute defined in `body common control` if
   available in 3.23.0