Syntax fixes

Author: hawkeyexl

docs/contributing/quick-start.mdx

@@ -19,18 +19,18 @@ Fix typos, broken links, and small issues directly in your browser—no setup re
 
 Every documentation page has an **Edit this page** link at the bottom. This is the fastest way to contribute.
 
-1. **Find the issue**: Navigate to the page with the problem.
-2. **Click "Edit this page"**: Located at the bottom of every doc page.
+1. __Find the issue__: Navigate to the page with the problem.
+2. __Open the editor__: Click **Edit this page**, located at the bottom of every doc page.
 
    GitHub opens the file in a web-based editor.
 
-3. **Make your changes**: Edit the Markdown file directly in the browser to fix the issue.
-4. **Preview your changes**: Open a preview panel (Ctrl+Shift+V) to see how it looks.
-5. **Commit your changes**:
+3. __Make your changes__: Edit the Markdown file directly in the browser to fix the issue.
+4. __Preview your changes__: Open a preview panel (Ctrl+Shift+V) to see how it looks.
+5. __Commit your changes__:
    1. In the side panel, click the **Source Control** button (looks like a branch icon).
    1. Add a brief description of what you changed (e.g., "Fix typo in installation steps").
    1. Click "Commit & Push".
-6. **Create a pull request**:
+6. __Create a pull request__:
    1. Review the changes one more time.
    1. In the Source Control panel, click the **Create Pull Request** button (looks like a vertical line with dots on both ends with an arrow pointing to the top and a plus sign).
    1. Enter a name and description for the pull request.
@@ -64,13 +64,13 @@ For different issues across different pages, create separate pull requests—it'
 
 ## What happens next
 
-1. **Automated checks**: Our CI/CD pipeline runs automated checks on your contribution
+1. __Automated checks__: Our CI/CD pipeline runs automated checks on your contribution
    - Style checks (Vale)
    - Link validation
    - Build verification
-2. **Review**: A maintainer reviews your changes (usually within 2 business days)
-3. **Feedback**: If changes are needed, the reviewer will comment on your pull request
-4. **Merge**: Once approved, your contribution is merged and goes live!
+2. __Review__: A maintainer reviews your changes (usually within 2 business days)
+3. __Feedback__: If changes are needed, the reviewer will comment on your pull request
+4. __Merge__: Once approved, your contribution is merged and goes live!
 
 ## Common contributor concerns (and why you don't need to worry)
 
@@ -81,9 +81,9 @@ For quick fixes like typos and link updates, no testing is required. The automat
 ### What if the automated checks fail?
 
 Don't worry! The reviewer will help you fix any issues. Most common failures are easily correctable:
-- **Vale failures**: Usually suggest alternative wording (often just suggestions)
-- **Link check failures**: Means a link is broken or inaccessible
-- **Build failures**: Usually means there's a syntax error in Markdown
+- __Vale failures__: Usually suggest alternative wording (often just suggestions)
+- __Link check failures__: Means a link is broken or inaccessible
+- __Build failures__: Usually means there's a syntax error in Markdown
 
 ### Can I edit multiple pages at once?
 
@@ -95,9 +95,9 @@ Yes, but only once. Before your first contribution can be merged, you'll be prom
 
 ## Need help?
 
-- **Questions about the change?** Ask in the pull request comments
-- **Not sure what to change?** Join our [Discord server](https://discord.gg/2M7wXEThfF)
-- **Found a bigger issue?** Consider a [standard contribution](standard-contributions) instead
+- __Questions about the change?__ Ask in the pull request comments
+- __Not sure what to change?__ Join our [Discord server](https://discord.gg/2M7wXEThfF)
+- __Found a bigger issue?__ Consider a [standard contribution](standard-contributions) instead
 
 ## Ready for more?