Apply suggestions from code review

Co-authored-by: Pedro Sousa <[email protected]>

Author: patriciasantaana

src/content/docs/style-guide/documentation-content-strategy/writing-guidelines.mdx

@@ -10,7 +10,7 @@ Use the following writing guidelines to create product content that is clear and
 
 ## Use plain language
 
-Plain language is writing that an audience can understand and act upon the first time they read it. Using plain language ensures your audience understands what you mean. Cloudflare users are a global audience whose first language might not be English. Plain language makes translation easier and documentation more accessible. Using plain language increases the chance that readers understand what you wrote the first time they read it.
+Plain language is writing that an audience can understand and act upon the first time they read it. Using plain language ensures your audience understands what you mean. Cloudflare users are a global audience whose first language might not be English. Plain language makes translation easier and documentation more accessible.
 
 Consider the following tips for using plain language in your writing:
 
@@ -75,7 +75,7 @@ Use present tense verbs. Avoid past tense whenever possible, as it can quickly m
 
 | Do | Don't | Rationale |
 | --- | --- | --- |
-| FindLaw **uses** Cloudflare to accelerate and secure thousands of customer sites. | FindLaw **used** Cloudflare to accelerate and secure thousands of customer sites. | FindLaw is a current customer who still benefits from the performance and security Cloudflare provides, so we should refer to them in the present tense |
+| FindLaw **uses** Cloudflare to accelerate and secure thousands of customer sites. | FindLaw **used** Cloudflare to accelerate and secure thousands of customer sites. | FindLaw is a current customer who still benefits from the performance and security Cloudflare provides, so we should refer to them in the present tense. |
 
 ---
 
@@ -92,12 +92,12 @@ Use the guidelines below to create product content that is more accessible to pe
 - Provide informative, unique page titles.
 - Use headings to convey meaning and structure.
 - Make the link text meaningful.
-- Writing meaningful text alternatives for images.
+- Writing meaningful text alternatives (alt text) for images.
 - Create transcripts and captions for multimedia.
 - Provide clear instructions.
 - Keep content clear and concise.
 
-Refer to [Writing for Web Accessibility](https://www.w3.org/WAI/tips/writing/) for additional information about  WCAG requirements, detailed background, user stories, and more.
+Refer to [Writing for Web Accessibility](https://www.w3.org/WAI/tips/writing/) for additional information about WCAG requirements, detailed background, user stories, and more.
 
 ---
 
@@ -107,7 +107,7 @@ Use simple language and formatting, as appropriate for the context. Respect our
 
 - Keep sentences between 8 to 12 words.
 - Write in short, clear sentences and paragraphs.
-- Avoid using unnecessarily complex words and phrases. Consider providing a glossary for terms readers may not know.
+- Avoid using unnecessarily complex words and phrases.
 - Expand acronyms on the first use. For example, Web Content Accessibility Guidelines (WCAG).
 - Consider providing a glossary for terms readers may not know.
 - Use list formatting as appropriate.
@@ -128,7 +128,7 @@ Participles are verbs that end in _-ed_ or _-ing_ and act as modifiers. Gerunds
 | Test the certificate **by using** a browser to connect to your server. | Test the certificate **using** a browser to connect to your server. |
 | When **you use** a load balancer with a public-facing IP address, this address becomes the IP address of your website. | When **using** a load balancer with a public-facing IP address, this address becomes the IP address of your website. |
 
-The last example illustrates a dangling modifier. In the "Don't" example, using does not have a subject, so the implied subject is address, which is incorrect. If the implied subject is not correct, you must revise the sentence to provide a subject for the modifying phrase.
+The last example illustrates a dangling modifier. In the "Don't" example, _using_ does not have a subject, so the implied subject is address, which is incorrect. If the implied subject is not correct, you must revise the sentence to provide a subject for the modifying phrase.
 
 The titles of tutorial or high-level process articles or topics typically start with a gerund. Titles have less context than sentences, so you must be especially careful to ensure that the meaning is clear.