diff --git a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/steps-tasks-procedures.mdx b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/steps-tasks-procedures.mdx
index a902c6366a977a..1e08c6dc805298 100644
--- a/src/content/docs/style-guide/documentation-content-strategy/component-attributes/steps-tasks-procedures.mdx
+++ b/src/content/docs/style-guide/documentation-content-strategy/component-attributes/steps-tasks-procedures.mdx
@@ -72,5 +72,5 @@ Use sentences like "The `<screen/page/card>` displays." wisely.
 
 Usually, you only need this kind of helper sentence if the user ended up in an unexpected location, or if there was more than one possible target location, depending on the options that the user selected.
 
-As an alternative, consider adding the `<screen/page/card>` mention at the beginning of the next step: "5. In `<screen/page/card>`, select Save." 
+As an alternative, consider adding the `<screen/page/card>` mention at the beginning of the next step: "5. In `<screen/page/card>`, select Save."
 :::
diff --git a/src/content/docs/style-guide/formatting/structure/paragraphs-and-line-breaks.mdx b/src/content/docs/style-guide/formatting/structure/paragraphs-and-line-breaks.mdx
index 6658947137f1cc..c28e5966490615 100644
--- a/src/content/docs/style-guide/formatting/structure/paragraphs-and-line-breaks.mdx
+++ b/src/content/docs/style-guide/formatting/structure/paragraphs-and-line-breaks.mdx
@@ -37,5 +37,5 @@ This is how the table looks:
 
 :::caution
 
-Do not use two spaces at the end of a sentence to create a forced line break. Although this Markdown syntax is supported, it is not immediately visible and can easily miss these line breaks during peer reviews. 
+Do not use two spaces at the end of a sentence to create a forced line break. Although this Markdown syntax is supported, it is not immediately visible and can easily miss these line breaks during peer reviews.
 :::
diff --git a/src/content/docs/style-guide/video/index.mdx b/src/content/docs/style-guide/video/index.mdx
index e06a40d02d44a1..d7e954db18f7a5 100644
--- a/src/content/docs/style-guide/video/index.mdx
+++ b/src/content/docs/style-guide/video/index.mdx
@@ -25,14 +25,14 @@ Videos should be recorded at 4K UHD. If 4K UHD is unavailable, Full HD footage m
 
 ##### Acceptable Resolutions
 
-- **4K Ultra HD:** 2160p (3840x2160)  
-- **2K Quad HD:** 1440p (2560x1440)  
-- **Full HD:** 1080p (1920x1080) 
+- **4K Ultra HD:** 2160p (3840x2160)
+- **2K Quad HD:** 1440p (2560x1440)
+- **Full HD:** 1080p (1920x1080)
 
 ##### Unacceptable Resolutions
 
-- **HD:** 720p (1280x720)  
-- **SD:** 480p (720x480)  
+- **HD:** 720p (1280x720)
+- **SD:** 480p (720x480)
 
 #### Frame Rate
 
@@ -81,7 +81,7 @@ Final videos should be graded to natural colors. They shouldn't be over or under
 
 #### **Examples of Poor Color Grading**
 
-<Flex> 
+<Flex>
 
 ![Too dark](~/assets/images/style-guide/video/too_dark.png)
 
@@ -99,9 +99,9 @@ Final videos should be graded to natural colors. They shouldn't be over or under
 
 #### **Examples of Good Color Grading**
 
-<Flex> 
+<Flex>
 
-![Warm tone](~/assets/images/style-guide/video/warm_tone.png) 
+![Warm tone](~/assets/images/style-guide/video/warm_tone.png)
 
 ![White Balanced](~/assets/images/style-guide/video/white_balanced.png)
 
@@ -151,7 +151,7 @@ Developer Documentation videos adhere to all brand guidelines.
 
 #### Intro and Outro
 
-Intros and outros are essential for structuring a video and guiding the audience through its content. 
+Intros and outros are essential for structuring a video and guiding the audience through its content.
 
 #### Transitions, Effects and Chapter Separators
 
@@ -169,10 +169,10 @@ In general, we rely on platform automatic subtitle generation (for example, YouT
 
 ##### Subtitle Specifications
 
-- Subtitles are always published in English in **SubRip format (.srt)**.  
-- Guidelines for subtitles:  
-  - Maximum **45 characters per line**.  
-  - Split over **2 lines** when necessary.  
+- Subtitles are always published in English in **SubRip format (.srt)**.
+- Guidelines for subtitles:
+  - Maximum **45 characters per line**.
+  - Split over **2 lines** when necessary.
   - Displayed for no longer than **10 seconds** per subtitle.
 
 #### Lower Thirds