update contributing path

Author: todortodorovic

.CONTRIBUTING/.CONTRIBUTING.md

@@ -67,6 +67,8 @@ Follow these steps when contributing documentation fixes, improvements, or new c
    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
@@ -78,17 +80,21 @@ Follow these steps when contributing documentation fixes, improvements, or new c
    - **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"
 
-   **If choosing Option B**: You must also enable "Allow edits from maintainers" when creating your PR (this option appears for PRs from forks). This allows our team to create a follow-up branch and handle style/formatting changes, letting you focus on the technical content.
+   **If choosing Option B**:
+   - If you enable "Allow edits from maintainers" when creating your PR (this option appears for PRs from forks), our team can perform changes directly on your branch
+   - If "Allow edits from maintainers" is not enabled, we will create the `follow-up/PR-[original_pr_number]` branch and go through the intermediary workflow described below
 
 ### Hand-off Process (Internal Team Workflow)
 
-When a contributor chooses Option B or becomes unresponsive during review:
+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:
 
 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
 
 When you modify content in the documentation, you should regenerate the AI-ready files to keep them current: