Changed several headings to be sentence case

Ticket: ENT-9964
Signed-off-by: Ole Herman Schumacher Elgesem <[email protected]>

Author: olehermanse

README.md

@@ -429,7 +429,7 @@ As a general note, avoiding abbreviations provides better readability.
 
 ## Technical reference documentation
 
-* follow the [Policy Style Guide](guide/writing-and-serving-policy/policy-style.markdown)
+* follow the [Policy style guide](guide/writing-and-serving-policy/policy-style.markdown)
   in examples and code snippets
 * use the appropriate lexer for syntax highlighting via Pygments
 
@@ -443,7 +443,7 @@ As a general note, avoiding abbreviations provides better readability.
 The structure of the technical documentation about CFEngine attributes,
 functions etc is as follows:
 
-### Promise Attributes
+### Promise attributes
 
 Promise attributes are documented within the respective promise types's reference
 page. Level-3 headers are used to start a new attribute (if the promise attribute
@@ -571,9 +571,9 @@ use the macro, and list the attributes explicitly:
     This argument does that.
 
 
-### Special Variables
+### Special variables
 
-Special Variables are documented within the page of their context.
+Special variables are documented within the page of their context.
 
     ### context.variable
 

api/enterprise-api-examples.markdown

@@ -11,7 +11,7 @@ tags: [examples, enterprise, REST, API, reporting]
 * [Managing settings][Managing settings]
 * [Browse host information][Browsing host information]
 * [Issue flexible SQL queries][SQL query examples] against data collected from hosts by the CFEngine Server
-* [Schedule reports][SQL query examples#Subscribed Query Example: Creating A Subscribed Query] for email and later download
+* [Schedule reports][SQL query examples#Subscribed query example: Creating a subscribed query] for email and later download
 * [Tracking changes performed by CFEngine][Tracking changes]
 
 **See also:** [Enterprise API reference][Enterprise API reference]

api/enterprise-api-examples/browsing-host-information.markdown

@@ -12,7 +12,7 @@ reports via [/api/query][Query REST API#Execute SQL query] for this. however, cu
 gathered from `cf-monitord`) is not part of the SQL reports data model.
 
 
-## Example: Listing Hosts With A Given Context
+## Example: Listing hosts with a given context
 
 **Request**
 
@@ -41,7 +41,7 @@ gathered from `cf-monitord`) is not part of the SQL reports data model.
       ]
     }
 
-## Example: Looking Up Hosts By Hostname
+## Example: Looking up hosts by hostname
 
 Contexts, also known as classes, are powerful.  You can use them to
 categorize hosts according to a rich set of tags. For example, each
@@ -74,7 +74,7 @@ for presentability).
     }
 
 
-#### Example: Looking Up Hosts By IP
+#### Example: Looking up hosts by IP
 
 Similarly we can lookup the host with hostname
 `windows2008-2.test.cfengine.com` by IP as follows (lines split and indented
@@ -104,7 +104,7 @@ for presentability).
     }
 
 
-## Example: Removing Host Data
+## Example: Removing host data
 
 If a host has been decommissioned from a Hub, we can explicitly remove data
 associated with the host from the Hub, by issuing a DELETE request (lines
@@ -123,7 +123,7 @@ SHA=1c8fafe478e05eec60fe08d2934415c81a51d2075aac27c9936e19012d625cb8 -X DELETE
 
 **See also:** [Host REST API][Host REST API#remove host from the hub]
 
-## Example: Listing Available Vital Signs For A Host
+## Example: Listing available vital signs for a host
 
 Each host record on the Hub has a set of vital signs collected by `cf-monitord`
 on the agent. We can view the list of vitals signs from as host as follows
@@ -172,7 +172,7 @@ SHA=4e913e2f5ccf0c572b9573a83c4a992798cee170f5ee3019d489a201bc98a1a/vital
         },
     }
 
-## Example: Retrieving Vital Sign Data
+## Example: Retrieving vital sign data
 
 Each vital sign has a collected time series of values for up to one week. Here
 we retrieve the time series for the `mem_free` vital sign at host

api/enterprise-api-examples/managing-settings.markdown

@@ -49,7 +49,7 @@ are managed by the LDAP API and not this Settings API.
     204 No Content
 
 
-## Example: Changing The Log Level
+## Example: Changing the log level
 
 The API uses standard Unix syslog to log a number of events. Additionally, log
 events are sent to `stderr`, which means they may also end up in your Apache

api/enterprise-api-examples/managing-users-and-roles.markdown

@@ -11,7 +11,7 @@ Roles are defined by regular expressions that determine which hosts the
 user can see, and what policy outcomes are restricted.
 
 
-## Example: Listing Users
+## Example: Listing users
 
 **Request**
 
@@ -47,7 +47,7 @@ user can see, and what policy outcomes are restricted.
     }
 
 
-## Example: Creating a New User
+## Example: Creating a new user
 
 All users will be created for the internal user table. The API will never
 attempt to write to an external LDAP server.
@@ -68,7 +68,7 @@ attempt to write to an external LDAP server.
     }
 
 
-## Example: Updating an Existing User
+## Example: Updating an existing user
 
 Both internal and external users may be updated. When updating an external
 users, the API will essentially annotate metadata for the user, it will never
@@ -84,7 +84,7 @@ credentials.
 
     204 No Content
 
-## Example: Retrieving a User
+## Example: Retrieving a user
 
 It is possible to retrieve data on a single user instead of listing
 everything. The following query is similar to issuing `GET
@@ -116,7 +116,7 @@ a regular expression for `id`.
       ]
     }
 
-## Example: Adding a User to a Role
+## Example: Adding a user to a role
 
 Adding a user to a role is just an update operation on the user. The full
 role-set is updated, so if you are only appending a role, you may want to
@@ -138,7 +138,7 @@ is used to remove a user from a role.
     }
 
 
-## Example: Deleting a User
+## Example: Deleting a user
 
 Users can only be deleted from the internal users table.
 

api/enterprise-api-examples/sql-queries.markdown

@@ -5,7 +5,7 @@ published: true
 tags: [examples, enterprise, rest, api, reporting, sql, queries]
 ---
 
-### Synchronous Example: Listing Hostname and IP for Ubuntu Hosts
+### Synchronous Example: Listing hostname and IP for Ubuntu hosts
 
 **Request:**
 
@@ -57,7 +57,7 @@ curl -k --user admin:admin https://test.cfengine.com/api/query -X POST -d '{ "qu
 }
 ```
 
-### Subscribed Query Example: Creating A Subscribed Query
+### Subscribed query example: Creating a subscribed query
 
 Here we create a new query to count file changes by name and have the result
 sent to us by email. The schedule field is any CFEngine context expression.
@@ -79,7 +79,7 @@ curl -k --user admin:admin https://test.cfengine.com/api/user/milton/ subscripti
 204 No Content
 ```
 
-### Subscribed Query Example: Listing Report Subscriptions
+### Subscribed query example: Listing report subscriptions
 
 Milton can list all his current subscriptions by issuing the following.
 
@@ -115,7 +115,7 @@ curl -k --user admin:admin https://test.cfengine.com/api/user/milton/subscriptio
 }
 ```
 
-### Subscribed Query Example: Removing A Report Subscription
+### Subscribed query example: Removing a report subscription
 
 **Request:**
 

api/enterprise-api-ref/export-import-api.markdown

@@ -7,7 +7,7 @@ tags: [reference, enterprise, API, import, export]
 
 Import & export API provides users the ability to transfer Mission Portal data between hubs.
 
-**See also:** [Export/Import Settings UI][Settings#Export/Import]
+**See also:** [Export/import Settings UI][Settings#Export/import]
 
 ## Get available items to export
 

api/enterprise-api-ref/federated-reporting-api.markdown

@@ -10,7 +10,7 @@ This API is used for configuring hubs so that a single hub can be used to report
 ## Remote hubs
 
 Federated reporting must be enabled before it is possible to use the remote hubs API, please
-see the `Enable hub for Federated reporting` section below.
+see the `Enable hub for federated reporting` section below.
 
 ### Remote hubs list
 
@@ -157,9 +157,9 @@ HTTP 202 ACCEPTED
 HTTP 202 ACCEPTED
 ```
 
-## Enable hub for Federated reporting
+## Enable hub for federated reporting
 
-### Enable hub as a Superhub
+### Enable hub as a superhub
 
 **URI:** https://hub.cfengine.com/api/fr/setup-hub/superhub
 
@@ -172,7 +172,7 @@ HTTP 202 ACCEPTED
 ```
 
 
-### Enable hub as a Feeder
+### Enable hub as a feeder
 
 **URI:** https://hub.cfengine.com/api/fr/setup-hub/feeder
 
@@ -206,7 +206,7 @@ HTTP 202 ACCEPTED
 ## Federation config
 
 Federated reporting must be enabled before generating or removing federation configuration, please
-see `Enable hub for Federated reporting` section above. Otherwise an error will be thrown and
+see `Enable hub for federated reporting` section above. Otherwise an error will be thrown and
 config file will not be created/deleted.
 
 ### Generate federation config

api/enterprise-api-ref/host.markdown

@@ -68,9 +68,9 @@ Host API allows to access host specific information.
 * **firstseen**
     Time of receiving the first status report from the client. It is equivalent to the time when the client have been bootstrapped to the server for the first time. Represented as UNIX TIMESTAMP.
 
-**Example usage:** `Example: Listing Hosts With A Given Context`, `Example: Looking Up Hosts By Hostname`, `Example: Looking Up Hosts By IP`
+**Example usage:** `Example: Listing hosts with a given context`, `Example: Looking up hosts by hostname`, `Example: Looking up hosts by IP`
 
-## Host Details
+## Host details
 
 **URI:** https://hub.cfengine.com/api/host/:host-id
 
@@ -357,7 +357,7 @@ Note: Collecting monitoring data by default is disabled.
 * **units**
     Units for the samples.
 
-**Example usage:** `Example: Listing Available Vital Signs For A Host`
+**Example usage:** `Example: Listing available vital signs for a host`
 
 ## Get samples from vital
 
@@ -420,7 +420,7 @@ Note: Collecting monitoring data by default is disabled.
 *   **values**
     Vital sign data. *(array of [ t, y ], where t is the sample timestamp)*
 
-**Example usage:** `Example: Retrieving Vital Sign Data`
+**Example usage:** `Example: Retrieving vital sign data`
 
 
 ## Get count of bootstrapped hosts by date range

api/enterprise-api-ref/inventory.markdown

@@ -6,7 +6,7 @@ tags: [reference, enterprise, API, reporting, URI]
 ---
 Inventory API allows to access inventory reports and attributes dictionary.
 
-## Inventory Reports
+## Inventory reports
 
 
 **URI:** https://hub.cfengine.com/api/inventory

api/enterprise-api-ref/query.markdown

@@ -87,7 +87,7 @@ API performance depend on the query result size, to achieve fastest results cons
 }
 ```
 
-**Example usage:**  `Synchronous Example: Listing Hostname and IP for Ubuntu Hosts`
+**Example usage:**  `Synchronous Example: Listing hostname and IP for Ubuntu hosts`
 
 ## Schedule SQL query as long running job
 

api/enterprise-api-ref/status-settings.markdown

@@ -154,4 +154,4 @@ administrator.
 }
 ```
 
-**Example usage:** `Example: Configuring LDAP`, `Example: Changing The Log Level`
+**Example usage:** `Example: Configuring LDAP`, `Example: Changing the log level`

api/enterprise-api-ref/users-rbac.markdown

@@ -76,7 +76,7 @@ API call allowed only for administrator.
 * **external**
     Is user from external source (LDAP/AD).
 
-**Example usage:** `Example: Listing Users`
+**Example usage:** `Example: Listing users`
 
 ## Get user data
 
@@ -125,7 +125,7 @@ API call allowed only for administrator.
 * **time_zone**
     Time zone
 
-**Example usage:** `Example: Retrieving a User`
+**Example usage:** `Example: Retrieving a user`
 
 ## Create new user
 
@@ -160,7 +160,7 @@ API call allowed only for administrator.
 }
 ```
 
-**Example usage:** `Example: Creating a New User`
+**Example usage:** `Example: Creating a new user`
 
 ## Update user
 
@@ -195,7 +195,7 @@ API call allowed only for administrator.
 }
 ```
 
-**Example usage:** `Example: Updating an Existing User`, `Example: Adding a User to a Role`
+**Example usage:** `Example: Updating an existing user`, `Example: Adding a user to a role`
 
 ## Delete user
 
@@ -206,7 +206,7 @@ API call allowed only for administrator.
 Remove internal user.
 API call allowed only for administrator.
 
-**Example usage:** `Example: Deleting a User`
+**Example usage:** `Example: Deleting a user`
 
 ## List RBAC roles