[pull] primary from flybywiresim:primary

docs/dev-corner/development-projects/documentation-project/documentation.md

@@ -43,11 +43,27 @@ To participate in the FlyByWire Documentation Project, you need to have the foll
     - mike
     - pillow
     - cairosvg
-- Install with this single line command:
+- Create and activate a Python Virtual Environment (`virtualenv`) to be used for working on the documentation project:
+    ```title="Run In Terminal"
+    python -m venv venv
+    ```
 
+    Once created, you need to activate it. Use the following command on Windows:
+    ```title="Activating virtualenv on Windows"
+    .\venv\Scripts\activate.bat
+    ```
+    Or the following command on Linux and macOS:
+    ```title="Activating virtualenv on Linux and macOS"
+    source venv/bin/activate
+    ```
+- Install dependencies with this single line command:
     ```title="Run In Terminal"
     pip install -r requirements.txt
     ```
+!!! info "Using `virtualenv`"
+    Starting with Python 3.11, the `pip` tool will fail to install dependencies and packages globally, instead it's recommended to use `virtualenv`. If you desire to install packages globally, you must use another tool, such as [`pipx`](https://github.com/pypa/pipx). We recommend using `virtualenv` because it's easier and the recommended way to work on Python projects.
+!!! danger "Activating `virtualenv`"
+    It's important to note that `virtualenv` activation is not persisted. If you restart your terminal/command prompt and want to preview your work on the documentation project again, you have to reactivate your `virutalenv` using the appropriate activation command that was shown earlier in this guide.
 !!! info "Pillow + Cairo Dependency"
     As part of the new social card feature released with `mkdocs-material 8.5.0` [Pillow](https://pillow.readthedocs.io/) and [Cairo Graphics](https://www.cairographics.org/) 
     dependencies were added. We bundle this as part of our `requirements.txt` to ensure the dependencies are installed when attempting to test [social cards locally](#social-cards-feature). If you encounter any issues with these python packages:

docs/pilots-corner/a32nx-briefing/mcdu/perf.md

@@ -40,7 +40,12 @@ Prompts on each PERF page:
             If the takeoff shift (see below) or the runway is changed after V1, V2 or VR insertion, but the origin airport remains the same, the MCDU message “CHECK TAKEOFF DATA” is displayed, but all takeoff parameters are retained.
 
     !!! tip
-        In the FlyByWire A32NX you can click on the LSK next to V1, VR and V2, to let the aircraft calculate the V-Speed for you. This calculated value is placed in the Scratchpad and can be moved to the V-Speed field with a second click. In real life, this value is usually calculated by a specific airline application on the EFB.
+        In the FlyByWire A32NX, pilots can calculate takeoff performance data via the flyPad. Visit our flyPad Performance Page guide for more information.
+
+        [flyPad Performance Page](../../../fbw-a32nx/feature-guides/flypados3/performance.md){target=new .md-button}
+
+        !!! warning "Not Available in the Stable Version; you can instead click on the LSK next to V1, VR and V2 to let the aircraft calculate the V-Speeds for you."
+
 
 - TRANS ALT (4L)
     - This field displays the navigation database default transition altitude (if defined) once the origin airport is entered. The pilot can modify it.