Apply suggestions from code review

Author: kodster28

src/content/docs/analytics/analytics-integrations/looker.mdx

@@ -53,7 +53,7 @@ To create your new LookML project:
 
 6. For **Starting Point**, choose \*Clone Public Git Repository\*\*.\*\*\*
 
-Enter the *Cloudflare_block* URL for the public Git repository `git://github.com/llooker/cloudflare_block.git`. 
+7. Enter the *cloudflare\_block* URL for the public Git repository `git://github.com/llooker/cloudflare_block.git`.
 
 8. Click **Create Project**. Looker will pull all of the repository files into a new LookML project.
 
@@ -66,7 +66,7 @@ Enter the *Cloudflare_block* URL for the public Git repository `git://github.com
 
 To update the connection name in the LookML files:
 
-1. In your LookML **Cloudflare_looker** model file, replace the **connection** name with yours, for example:
+1. In your LookML **cloudflare\_looker** model file, replace the **connection** name with yours, for example:
    `connection: "bigquery_lpr"`.
 
 2. Check if any table names need to be updated to your database connection names as well. If you decide to rename the filenames for explore, model name, and view, make sure to update all mentions within the other files. Otherwise, you might encounter errors.

src/content/docs/analytics/analytics-integrations/splunk.mdx

@@ -41,7 +41,7 @@ To install the [Cloudflare App for Splunk](https://splunkbase.splunk.com/app/450
 
    1. Open the setup screen by clicking the **Settings** dropdown, then click **Indexes**.
    2. Select **New Index**. Note that the **Indexes** page also gives you the status of all your existing indexes so that you can see whether you're about to use up your licensed amount of space.
-   3. Name the index **Cloudflare**, which is the default index that the Cloudflare App will use.
+   3. Name the index **cloudflare**, which is the default index that the Cloudflare App will use.
 
 7. Set up the HTTP Event Collector (HEC) on Splunk. To create an HEC:
 

src/content/docs/analytics/graphql-api/migration-guides/network-analytics-v2/index.mdx

@@ -67,7 +67,7 @@ For reference information on NAv2 nodes, refer to the [NAv2 node reference](/ana
 
 :::note[Obtaining data for ingress traffic only]
 
-All the NAv2 `*AnalyticsAdaptiveGroups` nodes include data for ingress and egress traffic. To obtain data about ingress traffic only, include `direction: 'ingress'` in your [GraphQL query filter](/analytics/graphql-api/features/filtering/).
+All the NAv2 `*AnalyticsAdaptiveGroups` nodes include data for ingress and egress traffic. To obtain data about ingress traffic only, include `direction: "ingress"` in your [GraphQL query filter](/analytics/graphql-api/features/filtering/).
 :::
 
 ## Schema comparison