Made all titles use sentence case instead of title case

This was inconsistent before, so I am trying to make it consistent.

Our preferred style is sentence case, so I am moving towards using
using that everywhere.

This commit only touches titles (not sub-headings within documents).

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

Author: olehermanse

api.markdown

@@ -16,4 +16,4 @@ API uses SQL. With the simplicity of REST and the flexibility of
 SQL, users can craft custom reports about systems of arbitrary scale, mining
 a wealth of data residing on globally distributed CFEngine Database Servers.
 
-See also the [Enterprise API Examples][Enterprise API Examples] and the [Enterprise API Reference][Enterprise API Reference].
+See also the [Enterprise API examples][Enterprise API examples] and the [Enterprise API reference][Enterprise API reference].

api/enterprise-api-examples.markdown

@@ -1,17 +1,17 @@
 ---
 layout: default
-title: Enterprise API Examples
+title: Enterprise API examples
 published: true
 sorting: 6
 tags: [examples, enterprise, REST, API, reporting]
 ---
 
-* [Check installation status][Checking Status]
-* [Manage users, roles][Managing Users and Roles]
-* [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
+* [Check installation status][Checking status]
+* [Manage users, roles][Managing users and roles]
+* [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
 * [Tracking changes performed by CFEngine][Tracking changes]
 
-**See also:** [Enterprise API Reference][Enterprise API Reference]
+**See also:** [Enterprise API reference][Enterprise API reference]

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

@@ -1,13 +1,13 @@
 ---
 layout: default
-title: Browsing Host Information
+title: Browsing host information
 published: true
 sorting: 50
 tags: [examples, enterprise, rest, api, reporting, hosts]
 ---
 
 A resource [/api/host][Host REST API#List hosts] is added as an alternative interface for browsing host
-information. For full flexibility we recommend using [SQL][SQL Schema]
+information. For full flexibility we recommend using [SQL][SQL schema]
 reports via [/api/query][Query REST API#Execute SQL query] for this. however, currently vital signs (data
 gathered from `cf-monitord`) is not part of the SQL reports data model.
 

api/enterprise-api-examples/checking-status.markdown

@@ -1,12 +1,12 @@
 ---
 layout: default
-title:  Checking Status
+title:  Checking status
 published: true
 sorting: 20
 tags: [examples, enterprise, rest, api, reporting, status]
 ---
 
-You can get basic info about the API by issuing [/api][Status and Settings REST API#Get server status]. This status
+You can get basic info about the API by issuing [/api][Status and settings REST API#Get server status]. This status
 information may also be useful if you contact support, as it gives some basic
 diagnostics.
 

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

@@ -1,6 +1,6 @@
 ---
 layout: default
-title:  Managing Settings
+title:  Managing settings
 published: true
 sorting: 30
 tags: [examples, enterprise, rest, api, reporting, settings, ldap]

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

@@ -1,6 +1,6 @@
 ---
 layout: default
-title:  Managing Users and Roles
+title:  Managing users and roles
 published: true
 sorting: 40
 tags: [examples, enterprise, rest, api, reporting, users, roles]

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

@@ -1,6 +1,6 @@
 ---
 layout: default
-title:  SQL Query Examples
+title:  SQL query examples
 published: true
 tags: [examples, enterprise, rest, api, reporting, sql, queries]
 ---

api/enterprise-api-ref.markdown

@@ -1,6 +1,6 @@
 ---
 layout: default
-title:  Enterprise API Reference
+title:  Enterprise API reference
 published: true
 sorting: 70
 tags: [reference, enterprise, REST, API, reporting, sql]
@@ -11,17 +11,17 @@ number of URI resources that support one or more GET, PUT, POST, or
 DELETE operations. While reporting is done using SQL, this query is
 always wrapped in a JSON request.
 
-**See also:** [Enterprise API Examples][Enterprise API Examples]
+**See also:** [Enterprise API examples][Enterprise API examples]
 
 ## Requests
 
 **GET** requests are one of **listing** or **getting**. **Listing** resources
 means that a number of results will be returned, but each entry may contain
-limited information. An example of a **listing** query is [/api/user][Users and Access-Control REST API#List users] to list
+limited information. An example of a **listing** query is [/api/user][Users and access-control REST API#List users] to list
 users. Notice that URI components are always non-plural. An exception to this
-is [/api/settings][Status and Settings REST API#Get settings], which returns the singleton resource for settings.
+is [/api/settings][Status and settings REST API#Get settings], which returns the singleton resource for settings.
 **Getting** a resource specifies an individual resource to return, e.g.
-[/api/user/homer][Users and Access-Control REST API#Get user data].
+[/api/user/homer][Users and access-control REST API#Get user data].
 
 **PUT** request typically create a new resource, e.g. a user.
 
@@ -86,9 +86,9 @@ All timestamps are reported in *Unix Time*, i.e. seconds since 1970.
 The API supports both internal and external authentication. The internal users
 table will always be consulted first, followed by an external source specified
 in the settings. External sources are *OpenLDAP* or *Active Directory* servers
-configurable through [/api/settings][Status and Settings REST API#Update settings].
+configurable through [/api/settings][Status and settings REST API#Update settings].
 
 
 ## Authorization
 
-Some resources require that the request user is a member of the *admin* role. Roles are managed with [/api/role][Users and Access-Control REST API#List RBAC roles]. Role Based Access Control (RBAC) is configurable through the settings. Users typically have permission to access their own resources, e.g. their own scheduled reports.
+Some resources require that the request user is a member of the *admin* role. Roles are managed with [/api/role][Users and access-control REST API#List RBAC roles]. Role Based Access Control (RBAC) is configurable through the settings. Users typically have permission to access their own resources, e.g. their own scheduled reports.

api/enterprise-api-ref/changes.markdown

@@ -162,7 +162,7 @@ List changes performed by CFEngine to the infrastructure. List can be narrowed d
 * **data.hostkey**
     Unique host identifier.
 * **data.hostname**
-    Host name locally detected on the host, configurable as `hostIdentifier` option in [Settings API][Status and Settings REST API#Get settings] and Mission Portal settings UI.
+    Host name locally detected on the host, configurable as `hostIdentifier` option in [Settings API][Status and settings REST API#Get settings] and Mission Portal settings UI.
 * **data.logmessages**
     List of 5 last messages generated during promise execution. Log messages can be used for tracking specific changes made by CFEngine while repairing or failing promise execution.
 * **data.policyfile**
@@ -174,7 +174,7 @@ List changes performed by CFEngine to the infrastructure. List can be narrowed d
 * **data.promiser**
     Object affected by a promise.
 * **data.promisetype**
-    [Type][Promise Types] of the promise.
+    [Type][Promise types] of the promise.
 * **data.stackpath**
     Call stack of the promise.
 

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

@@ -1,11 +1,11 @@
 ---
 layout: default
-title: Import & Export API
+title: Import & export API
 published: true
 tags: [reference, enterprise, API, import, export]
 ---
 
-Import & Export API provides users the ability to transfer Mission Portal data between hubs.
+Import & export API provides users the ability to transfer Mission Portal data between hubs.
 
 **See also:** [Export/Import Settings UI][Settings#Export/Import]
 
@@ -91,7 +91,7 @@ HTTP 200 Ok
 
 * **item_id** *(array)*
     Item id to be exported.
-    List of item ids you can obtain through [List of items to export][Import & Export API#Get available items to export]
+    List of item ids you can obtain through [List of items to export][Import & export API#Get available items to export]
         call described below.
 
 * **encryptionKey** *(string)*