update contributing

Author: todortodorovic

.CONTRIBUTING/.CONTRIBUTING.md

@@ -28,7 +28,7 @@ For tutorial contributions, please see our [tutorial contribution guidelines](.C
   - [Types of Contributions](#types-of-contributions)
   - [Contents](#contents)
   - [Contribution Workflow](#contribution-workflow)
-  - [Generating AI-Ready Documentation](#generating-ai-ready-documentation)
+    - [Generating AI-Ready Documentation](#generating-ai-ready-documentation)
   - [Viewing Site Locally](#viewing-site-locally)
     - [Clone Repositories](#clone-repositories)
     - [Install Dependencies and Serve Site](#install-dependencies-and-serve-site)
@@ -50,32 +50,39 @@ For tutorial contributions, please see our [tutorial contribution guidelines](.C
 Follow these steps when contributing documentation fixes, improvements, or new content:
 
 1. **Fork and Create Branch**
+
    ```bash
    git clone https://github.com/your-username/polkadot-docs.git
    cd polkadot-docs
    git checkout -b your-feature-branch
    ```
 
 2. **Make Your Changes**
+
    - Edit existing files or add new content
    - Follow the [style guide](https://github.com/papermoonio/documentation-style-guide/blob/main/style-guide.md)
    - Test your changes locally (see [Viewing Site Locally](#viewing-site-locally))
 
 3. **Generate Updated AI Documentation**
+
    After making content changes, regenerate the AI-ready documentation files:
+
    ```bash
    python3 scripts/generate_llms_standard.py
    ```
+
    This updates the `llms.txt` and `llms-full.txt` files that power our AI-ready documentation.
-   
+
    **Note**: This script needs to be run on every PR once all changes have been committed.
 
 4. **Create Pull Request**
+
    - Push your branch and create a pull request
    - Use the PR template to indicate your review preference
    - Include a clear description of your changes
 
 5. **Review Process Choice**
+
    In your pull request, please let us know:
    - **Option A**: "I have time to handle formatting and style review feedback myself"
    - **Option B**: "Please have the Polkadot docs team take over for formatting review to expedite the process"
@@ -86,24 +93,23 @@ Follow these steps when contributing documentation fixes, improvements, or new c
 
 ### Hand-off Process (Internal Team Workflow)
 
-When a contributor chooses Option B but does not have "Allow edits from maintainers" enabled, or when a contributor (regardless of option chosen) becomes unresponsive during review:
+When a contributor chooses Option B (or becomes unresponsive) and does not have "Allow edits from maintainers" enabled, the following workflow will apply:
 
 1. **Create Intermediary Branch**: Create a new branch named `follow-up/PR-[original_pr_number]`
 2. **Redirect Original PR**: Change the destination of the original PR to the intermediary branch
 3. **Complete Formatting Review**: Perform style and formatting reviews on the intermediary branch
 4. **Final Merge**: Merge the completed intermediary branch into master
 
-If the contributor selects Option B AND allows edits from maintainers then we can perform changes directly on the contributor's branch.
 
-## Generating AI-Ready Documentation
+### Generating AI-Ready Documentation
 
 When you modify content in the documentation, you should regenerate the AI-ready files to keep them current:
 
-### Prerequisites
+#### Prerequisites
 - Python 3.x installed
 - Required Python packages (run `pip install -r requirements.txt` in the project root)
 
-### Generate llms.txt Files
+#### Generate llms.txt Files
 ```bash
 cd /path/to/polkadot-docs
 python3 scripts/generate_llms_standard.py