Updates h7 and h8 formatting (elastic#118132)

docs/reference/connector/docs/connectors-box.asciidoc

@@ -54,7 +54,7 @@ For additional operations, see <<es-connectors-usage>>.
 ====== Box Free Account
 
 [discrete#es-connectors-box-create-oauth-custom-app]
-======= Create Box User Authentication (OAuth 2.0) Custom App
+*Create Box User Authentication (OAuth 2.0) Custom App*
 
 You'll need to create an OAuth app in the Box developer console by following these steps:
 
@@ -64,7 +64,7 @@ You'll need to create an OAuth app in the Box developer console by following the
 4. Once the app is created, *Client ID* and *Client secret* values are available in the configuration tab. Keep these handy.
 
 [discrete#es-connectors-box-connector-generate-a-refresh-token]
-======= Generate a refresh Token
+*Generate a refresh Token*
 
 To generate a refresh token, follow these steps:
 
@@ -97,7 +97,7 @@ Save the refresh token from the response. You'll need this for the connector con
 ====== Box Enterprise Account
 
 [discrete#es-connectors-box-connector-create-box-server-authentication-client-credentials-grant-custom-app]
-======= Create Box Server Authentication (Client Credentials Grant) Custom App
+*Create Box Server Authentication (Client Credentials Grant) Custom App*
 
 1. Register a new app in the https://app.box.com/developers/console[Box dev console] with custom App and select Server Authentication (Client Credentials Grant).
 2. Check following permissions:
@@ -224,7 +224,7 @@ For additional operations, see <<es-connectors-usage>>.
 ====== Box Free Account
 
 [discrete#es-connectors-box-client-create-oauth-custom-app]
-======= Create Box User Authentication (OAuth 2.0) Custom App
+*Create Box User Authentication (OAuth 2.0) Custom App*
 
 You'll need to create an OAuth app in the Box developer console by following these steps:
 
@@ -234,7 +234,7 @@ You'll need to create an OAuth app in the Box developer console by following the
 4. Once the app is created, *Client ID* and *Client secret* values are available in the configuration tab. Keep these handy.
 
 [discrete#es-connectors-box-client-connector-generate-a-refresh-token]
-======= Generate a refresh Token
+*Generate a refresh Token*
 
 To generate a refresh token, follow these steps:
 
@@ -267,7 +267,7 @@ Save the refresh token from the response. You'll need this for the connector con
 ====== Box Enterprise Account
 
 [discrete#es-connectors-box-client-connector-create-box-server-authentication-client-credentials-grant-custom-app]
-======= Create Box Server Authentication (Client Credentials Grant) Custom App
+*Create Box Server Authentication (Client Credentials Grant) Custom App*
 
 1. Register a new app in the https://app.box.com/developers/console[Box dev console] with custom App and select Server Authentication (Client Credentials Grant).
 2. Check following permissions:

docs/reference/connector/docs/connectors-content-extraction.asciidoc

@@ -183,7 +183,7 @@ Be aware that the self-managed connector will download files with randomized fil
 For that reason, we recommend using a dedicated directory for self-hosted extraction.
 
 [discrete#es-connectors-content-extraction-data-extraction-service-file-pointers-configuration-example]
-======= Example
+*Example*
 
 1. For this example, we will be using `/app/files` as both our local directory and our container directory.
 When you run the extraction service docker container, you can mount the directory as a volume using the command-line option `-v /app/files:/app/files`.
@@ -228,7 +228,7 @@ When using self-hosted extraction from a dockerized self-managed connector, ther
 * The self-managed connector and the extraction service will also need to share a volume. You can decide what directory inside these docker containers the volume will be mounted onto, but the directory must be the same for both docker containers.
 
 [discrete#es-connectors-content-extraction-data-extraction-service-file-pointers-configuration-dockerized-example]
-======= Example
+*Example*
 
 1. First, set up a volume for the two docker containers to share.
 This will be where files are downloaded into and then extracted from.

docs/reference/connector/docs/connectors-dropbox.asciidoc

@@ -190,7 +190,7 @@ When both are provided, priority is given to `file_categories`.
 We have some examples below for illustration.
 
 [discrete#es-connectors-dropbox-sync-rules-advanced-example-1]
-======= Example: Query only
+*Example: Query only*
 
 [source,js]
 ----
@@ -206,7 +206,7 @@ We have some examples below for illustration.
 // NOTCONSOLE
 
 [discrete#es-connectors-dropbox-sync-rules-advanced-example-2]
-======= Example: Query with file extension filter
+*Example: Query with file extension filter*
 
 [source,js]
 ----
@@ -225,7 +225,7 @@ We have some examples below for illustration.
 // NOTCONSOLE
 
 [discrete#es-connectors-dropbox-sync-rules-advanced-example-3]
-======= Example: Query with file category filter
+*Example: Query with file category filter*
 
 [source,js]
 ----
@@ -248,7 +248,7 @@ We have some examples below for illustration.
 // NOTCONSOLE
 
 [discrete#es-connectors-dropbox-sync-rules-advanced-limitations]
-======= Limitations
+*Limitations*
 
 * Content extraction is not supported for Dropbox *Paper* files when advanced sync rules are enabled.
 
@@ -474,7 +474,7 @@ When both are provided, priority is given to `file_categories`.
 We have some examples below for illustration.
 
 [discrete#es-connectors-dropbox-client-sync-rules-advanced-example-1]
-======= Example: Query only
+*Example: Query only*
 
 [source,js]
 ----
@@ -490,7 +490,7 @@ We have some examples below for illustration.
 // NOTCONSOLE
 
 [discrete#es-connectors-dropbox-client-sync-rules-advanced-example-2]
-======= Example: Query with file extension filter
+*Example: Query with file extension filter*
 
 [source,js]
 ----
@@ -509,7 +509,7 @@ We have some examples below for illustration.
 // NOTCONSOLE
 
 [discrete#es-connectors-dropbox-client-sync-rules-advanced-example-3]
-======= Example: Query with file category filter
+*Example: Query with file category filter*
 
 [source,js]
 ----
@@ -532,7 +532,7 @@ We have some examples below for illustration.
 // NOTCONSOLE
 
 [discrete#es-connectors-dropbox-client-sync-rules-advanced-limitations]
-======= Limitations
+*Limitations*
 
 * Content extraction is not supported for Dropbox *Paper* files when advanced sync rules are enabled.
 

docs/reference/connector/docs/connectors-github.asciidoc

@@ -210,7 +210,7 @@ Advanced sync rules are defined through a source-specific DSL JSON snippet.
 The following sections provide examples of advanced sync rules for this connector.
 
 [discrete#es-connectors-github-sync-rules-advanced-branch]
-======= Indexing document and files based on branch name configured via branch key
+*Indexing document and files based on branch name configured via branch key*
 
 [source,js]
 ----
@@ -226,7 +226,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-github-sync-rules-advanced-issue-key]
-======= Indexing document based on issue query related to bugs via issue key
+*Indexing document based on issue query related to bugs via issue key*
 
 [source,js]
 ----
@@ -242,7 +242,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-github-sync-rules-advanced-pr-key]
-======= Indexing document based on PR query related to open PR's via PR key
+*Indexing document based on PR query related to open PR's via PR key*
 
 [source,js]
 ----
@@ -258,7 +258,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-github-sync-rules-advanced-issue-query-branch-name]
-======= Indexing document and files based on queries and branch name
+*Indexing document and files based on queries and branch name*
 
 [source,js]
 ----
@@ -283,7 +283,7 @@ Check the Elasticsearch index for the actual document count.
 ====
 
 [discrete#es-connectors-github-sync-rules-advanced-overlapping]
-======= Advanced rules for overlapping
+*Advanced rules for overlapping*
 
 [source,js]
 ----
@@ -550,7 +550,7 @@ Advanced sync rules are defined through a source-specific DSL JSON snippet.
 The following sections provide examples of advanced sync rules for this connector.
 
 [discrete#es-connectors-github-client-sync-rules-advanced-branch]
-======= Indexing document and files based on branch name configured via branch key
+*Indexing document and files based on branch name configured via branch key*
 
 [source,js]
 ----
@@ -566,7 +566,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-github-client-sync-rules-advanced-issue-key]
-======= Indexing document based on issue query related to bugs via issue key
+*Indexing document based on issue query related to bugs via issue key*
 
 [source,js]
 ----
@@ -582,7 +582,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-github-client-sync-rules-advanced-pr-key]
-======= Indexing document based on PR query related to open PR's via PR key
+*Indexing document based on PR query related to open PR's via PR key*
 
 [source,js]
 ----
@@ -598,7 +598,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-github-client-sync-rules-advanced-issue-query-branch-name]
-======= Indexing document and files based on queries and branch name
+*Indexing document and files based on queries and branch name*
 
 [source,js]
 ----
@@ -623,7 +623,7 @@ Check the Elasticsearch index for the actual document count.
 ====
 
 [discrete#es-connectors-github-client-sync-rules-advanced-overlapping]
-======= Advanced rules for overlapping
+*Advanced rules for overlapping*
 
 [source,js]
 ----

docs/reference/connector/docs/connectors-ms-sql.asciidoc

@@ -196,7 +196,7 @@ Here are a few examples of advanced sync rules for this connector.
 ====
 
 [discrete#es-connectors-ms-sql-sync-rules-advanced-queries]
-======= Example: Two queries
+*Example: Two queries*
 
 These rules fetch all records from both the `employee` and `customer` tables. The data from these tables will be synced separately to Elasticsearch.
 
@@ -220,7 +220,7 @@ These rules fetch all records from both the `employee` and `customer` tables. Th
 // NOTCONSOLE
 
 [discrete#es-connectors-ms-sql-sync-rules-example-one-where]
-======= Example: One WHERE query
+*Example: One WHERE query*
 
 This rule fetches only the records from the `employee` table where the `emp_id` is greater than 5. Only these filtered records will be synced to Elasticsearch.
 
@@ -236,7 +236,7 @@ This rule fetches only the records from the `employee` table where the `emp_id`
 // NOTCONSOLE
 
 [discrete#es-connectors-ms-sql-sync-rules-example-one-join]
-======= Example: One JOIN query
+*Example: One JOIN query*
 
 This rule fetches records by performing an INNER JOIN between the `employee` and `customer` tables on the condition that the `emp_id` in `employee` matches the `c_id` in `customer`. The result of this combined data will be synced to Elasticsearch.
 
@@ -484,7 +484,7 @@ Here are a few examples of advanced sync rules for this connector.
 ====
 
 [discrete#es-connectors-ms-sql-client-sync-rules-advanced-queries]
-======= Example: Two queries
+*Example: Two queries*
 
 These rules fetch all records from both the `employee` and `customer` tables. The data from these tables will be synced separately to Elasticsearch.
 
@@ -508,7 +508,7 @@ These rules fetch all records from both the `employee` and `customer` tables. Th
 // NOTCONSOLE
 
 [discrete#es-connectors-ms-sql-client-sync-rules-example-one-where]
-======= Example: One WHERE query
+*Example: One WHERE query*
 
 This rule fetches only the records from the `employee` table where the `emp_id` is greater than 5. Only these filtered records will be synced to Elasticsearch.
 
@@ -524,7 +524,7 @@ This rule fetches only the records from the `employee` table where the `emp_id`
 // NOTCONSOLE
 
 [discrete#es-connectors-ms-sql-client-sync-rules-example-one-join]
-======= Example: One JOIN query
+*Example: One JOIN query*
 
 This rule fetches records by performing an INNER JOIN between the `employee` and `customer` tables on the condition that the `emp_id` in `employee` matches the `c_id` in `customer`. The result of this combined data will be synced to Elasticsearch.
 

docs/reference/connector/docs/connectors-network-drive.asciidoc

@@ -174,7 +174,7 @@ Advanced sync rules for this connector use *glob patterns*.
 The following sections provide examples of advanced sync rules for this connector.
 
 [discrete#es-connectors-network-drive-indexing-files-and-folders-recursively-within-folders]
-======= Indexing files and folders recursively within folders
+*Indexing files and folders recursively within folders*
 
 [source,js]
 ----
@@ -190,7 +190,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-network-drive-indexing-files-and-folders-directly-inside-folder]
-======= Indexing files and folders directly inside folder
+*Indexing files and folders directly inside folder*
 
 [source,js]
 ----
@@ -203,7 +203,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-network-drive-indexing-files-and-folders-directly-inside-a-set-of-folders]
-======= Indexing files and folders directly inside a set of folders
+*Indexing files and folders directly inside a set of folders*
 
 [source,js]
 ----
@@ -216,7 +216,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-network-drive-excluding-files-and-folders-that-match-a-pattern]
-======= Excluding files and folders that match a pattern
+*Excluding files and folders that match a pattern*
 
 [source,js]
 ----
@@ -432,7 +432,7 @@ Advanced sync rules for this connector use *glob patterns*.
 The following sections provide examples of advanced sync rules for this connector.
 
 [discrete#es-connectors-network-drive-client-indexing-files-and-folders-recursively-within-folders]
-======= Indexing files and folders recursively within folders
+*Indexing files and folders recursively within folders*
 
 [source,js]
 ----
@@ -448,7 +448,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-network-drive-client-indexing-files-and-folders-directly-inside-folder]
-======= Indexing files and folders directly inside folder
+*Indexing files and folders directly inside folder*
 
 [source,js]
 ----
@@ -461,7 +461,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-network-drive-client-indexing-files-and-folders-directly-inside-a-set-of-folders]
-======= Indexing files and folders directly inside a set of folders
+*Indexing files and folders directly inside a set of folders*
 
 [source,js]
 ----
@@ -474,7 +474,7 @@ The following sections provide examples of advanced sync rules for this connecto
 // NOTCONSOLE
 
 [discrete#es-connectors-network-drive-client-excluding-files-and-folders-that-match-a-pattern]
-======= Excluding files and folders that match a pattern
+*Excluding files and folders that match a pattern*
 
 [source,js]
 ----