Enhance documentation for DVR and Workflows

src/content/changelog/stream/2025-02-14-introducing-dvr-for-stream-live.mdx

@@ -11,7 +11,7 @@ Previously, all viewers watched "the live edge," or the latest content of the
 broadcast, synchronously. If a viewer paused for more than a few seconds,
 the player would automatically "catch up" when playback started again. Seeking
 through the broadcast was only available once the recording was available after
-it conluded.
+  it concluded.
 
 Starting today, customers can make a small adjustment to the player
 embed or manifest URL to enable the DVR experience for their viewers. By

src/content/changelog/workers/2025-01-31-html-rewriter-streaming.mdx

@@ -1,6 +1,6 @@
 ---
 title: Transform HTML quickly with streaming content
-description: HTMLRewiter now supports streamed content for more efficient replacement of HTML elements
+description: HTMLRewriter now supports streamed content for more efficient replacement of HTML elements
 products:
   - workers
 date: 2025-01-31T01:00:00Z

src/content/changelog/workflows/2024-10-24-workflows-beta.mdx

@@ -11,7 +11,7 @@ import { Render, PackageManagers } from "~/components"
 
 Workflows is now in open beta, and available to any developer a free or paid Workers plan.
 
-Workflows allow you to build multi-step applications that can automatically retry, persist state and run for minutes, hours, days, or weeks. Workflows introduces a programming model that makes it easier to build reliable, long-running tasks, observe as they progress, and programatically trigger instances based on events across your services. 
+Workflows allow you to build multi-step applications that can automatically retry, persist state and run for minutes, hours, days, or weeks. Workflows introduces a programming model that makes it easier to build reliable, long-running tasks, observe as they progress, and programmatically trigger instances based on events across your services.
 
 ### Get started
 

src/content/docs/1.1.1.1/other-ways-to-use-1.1.1.1/dns-over-discord.mdx

@@ -189,7 +189,7 @@ As with the `/dig` command, any user can press the refresh button to refresh the
 
 Like the `/dig` command, you can change the DNS provider when using the `/multi-dig` command. The menu appears after each set of DNS results (or after each block of results if more than 10 record types are requested).
 
-This menu can be used be any user to change the DNS provider used for the lookup.
+This menu can be used by any user to change the DNS provider used for the lookup.
 
 ## `whois` command
 

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

@@ -73,7 +73,7 @@ For example: `https://prd-p-0qk3h.splunkcloud.com:8088/services/collector/raw`.
 
 **Post Installation Notes**
 
-You can change the **Index Name** after the initial configuration by clicking on the **Settings** dropdown and navigating to **Advance search**. There you can select **Search macros** and look for the Cloudflare App for Splunk.
+You can change the **Index Name** after the initial configuration by clicking on the **Settings** dropdown and navigating to **Advanced search**. There you can select **Search macros** and look for the Cloudflare App for Splunk.
 
 ![Splunk interface highlighting Apps menu and Manage Apps option along with Enable Acceleration checkbox](~/assets/images/fundamentals/splunk/screenshots/splunk-settings-advanced-search-search-macros.png)