updated actions and skipped hookes to fail on github.

Signed-off-by: René <snooz@posteo.de>

Author: Snooz82

.github/workflows/pr-preview-surge.yml

@@ -44,6 +44,15 @@ jobs:
         with:
           fetch-depth: 0
 
+      - name: Set up Python
+        uses: actions/setup-python@v5
+        with:
+          python-version: '3.11'
+
+      - name: Check numbering and links
+        run: python tools/gen_numbering.py
+        working-directory: .
+
       - name: Use Node.js
         uses: actions/setup-node@v4
         with:

CONTRIBUTION.md

@@ -13,10 +13,7 @@ Thanks for helping us improve the RFCP syllabus! The notes below explain how to
    python bootstrap.py
    ```
    The script upgrades `pip`, installs `pre-commit`, and asks whether you want to pull in the optional PDF toolchain (Robot Framework + Browser batteries from `requirements.txt`, plus Chromium via `rfbrowser install chromium`). Answer "y" only if you plan to regenerate the PDF. Regardless of that choice, the script installs the pre-commit hook and then runs `npm install` inside `website/` so Docusaurus has its dependencies.
-2. Activate the freshly created virtual environment so local commands use the same interpreters as the hooks:
-   - macOS/Linux: `source .venv/bin/activate`
-   - Windows (PowerShell): `.venv\Scripts\Activate.ps1`
-3. Start Docusaurus in development mode while you edit:
+2. Start Docusaurus in development mode while you edit:
    ```bash
    cd website  # if not already there
    npm run start
@@ -28,10 +25,16 @@ Thanks for helping us improve the RFCP syllabus! The notes below explain how to
 - Docusaurus validates internal links during builds. Run `npm run build` before submitting a PR to catch broken anchors or missing pages early.
 
 ## 4. Generating the syllabus PDF
-To rebuild the certification PDF from the Robot Framework assets, run the Robot Framework suite from the repo root:
-```bash
-robot -d results tools/gen_pdf.robot
-```
+To rebuild the syllabus PDF from the Robot Framework assets, run the Robot Framework suite from the repo root:
+
+1. Activate the created virtual environment so local commands use the same interpreters as the hooks:
+   - macOS/Linux: `source .venv/bin/activate`
+   - Windows (PowerShell): `.venv\Scripts\Activate.ps1`
+
+2. Run the suite to generate the PDF:
+    ```bash
+    robot -d results tools/gen_pdf.robot
+    ```
 The PDF and execution logs land inside `results/`.
 
 Following the steps above keeps your local environment consistent with CI and ensures contributions land cleanly. Happy writing!

LOs.csv

@@ -10,7 +10,7 @@ LO-1.3.4,(K1),Recall the difference between Resource Files and Libraries and the
 LO-1.4,(K1),Recall the three specification styles of Robot Framework,,,
 LO-1.4.1,(K2),Understand the basic concepts of Keyword-Driven Specification,,,
 LO-1.4.2,(K2),Understand the basic concepts of Behavior-Driven Specification,,,
-LO-1.4.3,(K1),Recall the differences between Keyword-Driven and Behavior-Driven Specification,,,
+LO-1.4.3,(K1),Recall the differenceaasdasds between Keyword-Driven and Behavior-Driven Specification,,,
 LO-1.4.4,(K1),Recall the purpose of Data-Driven Specification,,,
 LO-1.5.1,(K1),Recall the type of open-source license under which Robot Framework is distributed,,,
 LO-1.5.2,(K1),List and recall the key objectives and organizational form of the Robot Framework Foundation,,,