Skip to content

Remove trailing spaces #22810

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jun 2, 2025
Merged

Remove trailing spaces #22810

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .../documentation-content-strategy/component-attributes/steps-tasks-procedures.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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."
:::
2 changes: 1 addition & 1 deletion src/content/docs/style-guide/formatting/structure/paragraphs-and-line-breaks.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
:::
26 changes: 13 additions & 13 deletions src/content/docs/style-guide/video/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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)

Expand All @@ -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)

Expand Down Expand Up @@ -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

Expand All @@ -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
Expand Down
Loading