### Markdown: Global Content Best Practices Examples

Source: https://context7.com/microsoftdocs/microsoft-style-guide/llms.txt

Provides Markdown examples for global content best practices, focusing on date and time formats, and currency. This aids in creating documentation that is clear and unambiguous for international audiences.

```markdown
## Global Content Best Practices

### Date and time formats
**Use**: Month DD, YYYY format for clarity
**Avoid**: Ambiguous numeric dates (MM/DD/YY)

**Example**:
Preferred: "January 15, 2024"
Avoid: "01/15/24" (ambiguous to international readers)

### Currency
**First mention**: Use currency code
**Be specific**: Avoid assumptions about default currency

**Example**:
Correct: "Pricing starts at $9.99 USD per month"
Also acceptable: "Pricing starts at 9.99 USD"
```

--------------------------------

### Using Placeholders in Syntax and User Input

Source: https://github.com/microsoftdocs/microsoft-style-guide/blob/main/styleguide/procedures-instructions/formatting-text-in-instructions.md

Placeholders in syntax or user input should be represented using italics. This visually distinguishes them from literal text or commands. Examples include version numbers or passwords.

```text
/v: *version*
Enter *password*.
```

--------------------------------

### Markdown: Punctuation Rules Examples

Source: https://context7.com/microsoftdocs/microsoft-style-guide/llms.txt

Provides examples of Markdown syntax for illustrating punctuation rules, including commas, colons, em dashes, periods, and apostrophes. This is useful for documentation generation where Markdown is the source format.

```markdown
## Punctuation Rules

### Commas
**Oxford comma**: Always use in lists of three or more items
**Example**:
Wrong: "Available on Windows, Mac and Linux"
Right: "Available on Windows, Mac, and Linux"

### Colons
**Use**: Introduce lists, explanations, or examples
**Don't use**: After headings or in place of periods

**Example**:
Correct: "System requirements: 8 GB RAM, 256 GB storage"
Correct: "Follow these steps: sign in, select settings, choose options"

### Em dashes
**Use**: Set off emphasizing or interrupting information
**No spaces**: Place directly adjacent to text

**Example**:
Correct: "Microsoft 365—formerly Office 365—includes cloud services"
Wrong: "Microsoft 365 — formerly Office 365 — includes cloud services"

### Periods
**Use**: End sentences in body text
**Don't use**: After headings, list items under 3 words, UI labels

**Example**:
Correct heading: **Save your work**
Wrong heading: **Save your work.**

Correct list:
- Quick access
- Easy sharing
- Automatic backup

### Apostrophes
**Contractions**: Use for friendly tone
**Possessives**: Follow standard rules

**Example**:
Contractions: "you're", "it's", "we'll", "let's"
Possessives: "user's profile", "app's features", "companies' data"
```