Fix block description In-consistency

[Infinite-Null]

Closes: #69475

What?

This PR standardizes block descriptions in the /packages/block-library directory, ensuring verb tense and structure consistency.

Why?

Some descriptions use different verb tenses (e.g., “Display” vs. “Displays”). This PR aims to standardize descriptions using a third-person verb format where applicable.

How?

• Updated descriptions that start with a verb to use third-person singular (e.g., “Displays” instead of “Display”).
• Ensured consistency across all block descriptions in the block library.

Testing Instructions

1. Search for the description in block.json in /packages/block-library.
2. Also you can open the block editor and inspect block descriptions in the block settings panel.
3. Compare the description changes to ensure consistency.

[github-actions]

Warning: Type of PR label mismatch

To merge this PR, it requires exactly 1 label indicating the type of PR. Other labels are optional and not being checked here.

• Type-related labels to choose from: [Type] Automated Testing, [Type] Breaking Change, [Type] Bug, [Type] Build Tooling, [Type] Code Quality, [Type] Copy, [Type] Developer Documentation, [Type] Enhancement, [Type] Experimental, [Type] Feature, [Type] New API, [Type] Task, [Type] Technical Prototype, [Type] Performance, [Type] Project Management, [Type] Regression, [Type] Security, [Type] WP Core Ticket, Backport from WordPress Core, Gutenberg Plugin.
• Labels found: .

Read more about Type labels in Gutenberg. Don't worry if you don't have the required permissions to add labels; the PR reviewer should be able to help with the task.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: Infinite-Null <[email protected]>
Co-authored-by: afercia <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.