More minor edits

Author: lcawl

contribute-docs/style-guide/accessibility.md

@@ -190,33 +190,32 @@ Different people are used to different names, currencies, date and time formats,
 * Avoid ambiguous values, like `04/05/06` for a date. Is it May 4 or April 5, and which year? `11/17/1987` leaves less room for interpretation if the exact format is not specified nearby. 
 * If there is no obvious example standard (RFC) to follow, try to be diverse to represent our audience.
 
-✔️ **Avoid idioms or expressions that are not commonly known, also known as regionalisms.** 
+✔️ **Avoid idioms or expressions that are not commonly known, also known as regionalisms.**
 
-In our Elastic documentation, we aim for a fun, friendly, and sometimes quirky 
-tone. To achieve that, it can help to use informal, playful language. However, 
-we also have to be careful that our text is as inclusive as possible, so we try 
-to avoid expressions that might be unknown or opaque to some readers. Here are 
-a few examples of what to avoid:
+In our Elastic documentation, we aim for a fun, friendly, and sometimes quirky tone.
+To achieve that, it can help to use informal, playful language.
+However, we also have to be careful that our text is as inclusive as possible, so we try to avoid expressions that might be unknown or opaque to some readers.
+Here are a few examples of what to avoid:
 
 * Idioms (for example, _It's a piece of cake_ or _So far so good_)
 * Regional expressions (for example, _G'day!_, _Y'all_, or _eh_)
 * Sports expressions (for example, _touched base_ or _threw a curve ball_)
 * Pop culture references (for example, _Elvis has left the building_ or _Same bat-time, same bat-channel_)
 
-We're all pretty good at avoiding these, but there's one problematic type of 
-expression that shows up frequently in docs reviews. Latin terms and 
-abbreviations are a common source of confusion, particularly for people whose 
-first language does not have Latin roots.
+We're all pretty good at avoiding these, but there's one problematic type of expression that shows up frequently in docs reviews.
+Latin terms and abbreviations are a common source of confusion, particularly for people whose first language does not have Latin roots.
 
 Here are some terms to avoid and suggested alternatives:
 
 | Avoid | Use instead |
 | ----- | ----------- |
-| e.g. (exempli gratia) | For example | 
+| e.g. (exempli gratia) | For example |
 | etc. (et cetera) | And more, and so on |
 | i.e. (id est) | That is |
 | via | By way of, by means of, through |
 
+For more examples, refer to [](/contribute-docs/style-guide/word-choice.md)
+
 ✔️ **Aim for readability.** Tools like the Hemingway App can help you make content simpler. Be conversational, but prioritize clarity.
 
 #### Use gender-neutral language

contribute-docs/style-guide/grammar-spelling.md

@@ -431,6 +431,8 @@ Avoid Latin abbreviations for common English phrases, unless space is limited.
 ✔️ **Do**: for example
 :::
 
+For more examples, refer to [](/contribute-docs/style-guide/word-choice.md)
+
 ## Glossary
 
 For a list of terms and abbreviations commonly used in our docs, refer to the [Glossary](/reference/glossary/index.md).

contribute-docs/style-guide/seo.md

@@ -191,7 +191,7 @@ Best practices:
 
   * Use structured data (for example, [schema.org](https://schema.org/) markup) to add semantic meaning.  
     Structured data can help search engines display your documentation in rich results, such as FAQs or How-To snippets.  
-    Check with the documentation team for existing capabilities or implementation guidance.
+    Check with the documentation team for existing capabilities or implementation guidance. If you're an external contributor, open a GitHub issue to discuss implementation options.
 
 ### Content length
 
@@ -253,7 +253,6 @@ Best practices:
 
 * Accessibility considerations
 
-  * Use semantic HTML (`<ul>`, `<ol>`, `<li>`) for lists.  
   * Avoid using lists for layout or decorative purposes.
 
 ### Interlinking
@@ -277,7 +276,6 @@ Best practices:
 * Use external links judiciously
 
   * Link to reputable, authoritative sources when necessary. For example, `https://www.python.org/doc/`.
-  * Ensure external links open in a new tab/window.
 
 * Maintain link accessibility
 
@@ -351,9 +349,7 @@ Best practices:
   * Avoid unnecessary words or parameters.  
   * Use hyphens (-) to separate words for clarity.
 
-* Use lowercase letters
-
-  * Always use lowercase to prevent duplicate content issues (e.g., /Guide/ vs. /guide/).
+* Always use lowercase to prevent duplicate content issues.
 
 * Avoid special characters