docs(release): v0.11.0 release notes

docs/dev-corner/dev-guide/resources.md

@@ -10,7 +10,7 @@ The main GitHub repository for the A32NX aircraft is:
 
 The Development version of the FlyByWire A32NX is done in the master branch. Whenever something is merged into the master branch, an automatic build process builds the newest 
 Development version and uploads it to our CDN, so users can download the latest Development version via the FlyByWire Installer. We have a very strict development, review and 
-QA process for for this version.
+QA process for this version.
 
 The Stable version is a snapshot (in git terms, a [Tag](https://github.com/flybywiresim/aircraft/tags){target=new}) of the development branch.
 

docs/fbw-a32nx/feature-guides/cFMS.md

@@ -87,8 +87,8 @@ Please see our [Flight Planning in MSFS Guide](flight-planning.md) for more info
 ## WX/TER
 
 !!! info "Important Notice"
-    - TCAS is now available in the Development version.
-    - Terrain Radar is now available in the Development version via [SimBridge](../../index.md).
+    - TCAS is now available in the all versions.
+    - Terrain Radar is now available in the all versions via [SimBridge](../../index.md).
     - Please see our [CFMS NOTAM](https://flybywiresim.com/notams/cfms/) for further WX/TER information.
 
 It is important to note that the weather radar is not available yet with the latest version of our cFMS(v1.5). Our current focus is to deliver a more realistic flight planning and navigation experience while maintaining performance and reliability. However, we are not satisfied with how the default code performs together with our custom systems.

docs/fbw-a32nx/feature-guides/flypados3/index.md

@@ -1,6 +1,6 @@
 ---
 title: flyPadOS 3 EFB - Overview
-description: A guide to the flyPadOS 3 EFB used in the Development version of the A32NX.
+description: A guide to the flyPadOS 3 EFB used in the A32NX.
 ---
 
 <link rel="stylesheet" href="../../../../stylesheets/efb-interactive.css">
@@ -28,7 +28,7 @@ description: A guide to the flyPadOS 3 EFB used in the Development version of th
 !!! warning "Please Note"
     This guide covers the flyPad version and features available in the latest FlyByWire [Development Version](../../fbw-versions.md#version-overview).
 
-    If you use the FlyByWire Stable version, you might not have these features available.
+    If you use the FlyByWire Stable version, you might not have all features available. This will be appropriately flagged throughout our documentation.
 
 !!! abstract "From Wikipedia: [Electronic Flight Bag](https://en.wikipedia.org/wiki/Electronic_flight_bag){target=new}:"
 

docs/fbw-a32nx/feature-guides/flypados3/settings.md

@@ -234,12 +234,6 @@ Settings for integrations with various 3rd party applications
     <span class="imagesub">Click on the menu icons in this image to see other flyPad pages.</span>
 </div>
 
-[//]: # (!!! warning "")
-
-[//]: # (    This feature is only available in the [Development Version]&#40;../../fbw-versions.md#development-version-recommended&#41;)
-!!! warning "Navigraph Options"
-    This feature is only available in the [Development Version](../../fbw-versions.md#development-version-recommended)
-
 #### GSX Integration
 These options are separate to provide you with the flexibility to choose what to sync with GSX and what not to sync. 
 
@@ -300,19 +294,10 @@ Settings for integration with various data and information sources.
 
         ![flypad-settings-atsu-aoc-telex-warning](../../assets/flypados3/flypad-settings-atsu-aoc-telex-warning.png)
 
-- SimBrief Username/Pilot ID (**Stable Version Only**)
-    - See [next chapter](#simbrief-integration)
 - Hoppie User ID:
     - Unique logon code that is used to identify the user for the Hoppie ACARS communication.
     - See [Create a logon code](../hoppie.md#create-a-logon-code) in our documentation for Hoppie ACARS.
 
-### SimBrief Integration
-
-!!! warning ""
-    This setting only applies to the Stable Version of the A32NX. See the page listed below.
-
-Please see our [SimBrief and Navigraph Integration](../simbrief.md) page for details on linking your accounts for both Stable and Development Versions.
-
 ## Audio
 
 Settings for various audio sources and sounds.

docs/fbw-a32nx/feature-guides/gsxintegration/index.md

@@ -1,6 +1,6 @@
 ---
 title: GSX Integration - Overview
-description: A guide to the GSX Integration provided in the development version.
+description: A guide to the GSX Integration provided in the A32NX.
 ---
 
 <link rel="stylesheet" href="../../../../stylesheets/efb-interactive.css">
@@ -13,7 +13,7 @@ description: A guide to the GSX Integration provided in the development version.
 !!! warning "Please Note"
     This guide covers GSX Integration and the features available in the latest FlyByWire [Development Version](../../fbw-versions.md#development-version-recommended).
 
-    If you use the FlyByWire Stable version, you might not have these features available.
+    If you use the FlyByWire Stable version, you might not have all features available. This will be appropriately flagged throughout our doucmentation.
 
 !!! danger "Support"
     The FlyByWire team does not take responsibility for bugs encountered while using GSX. 

docs/fbw-a32nx/feature-guides/hoppie.md

@@ -2,17 +2,11 @@
 
 !!! warning "Requires credentials with Hoppie service"
 
-The Hoppie ACARS system is a complex system, and we have decided to develop and release it step-by-step. 
-
-[//]: # (So please be aware that not all features are available in the early releases and there may be differences between the **Stable Version** and **Development Version** as outlined below. We will add additional functionality over time.)
-
-[//]: # (???+ tip "Development Version - Features (Click to Open)")
-
-[//]: # (    Our development version has the following features:)
+The Hoppie ACARS system is a complex system, and we have decided to develop and release it step-by-step.
 
 ??? tip "Stable Version - Features (Click to Open)"
     !!! danger ""
-        This section will be current for Stable version 0.10.0. Any changes to our development branch will be noted with the appropriate flag or indicator. Please be aware of any differences when 
+        This section will be current for Stable version 0.11.0. Any changes to our development branch will be noted with the appropriate flag or indicator. Please be aware of any differences when 
         using our CPDLC implementation.
 
     The current version has the following features:

docs/fbw-a32nx/feature-guides/index.md

@@ -14,11 +14,17 @@ It is not a complete collection of all features, but a growing list which is ext
 | Quick Links                                               |
 |:----------------------------------------------------------|
 | [Autopilot and Fly-By-Wire](autopilot-fbw.md)             |
+| [Custom FMS](cFMS.md)                                     |
 | [Flight Management System](cFMS.md)                       |
 | [Free Text](freetext.md)                                  |
 | [Fuel and Weight](loading-fuel-weight.md)                 |
+| [GSX Integration](gsxintegration/index.md)                |
 | [Hoppie ACARS](hoppie.md)                                 |
 | [MCDU Keyboard Support](mcdu-keyboard.md)                 |
 | [Nose Wheel and Tiller Operation](nw-tiller.md)           |
 | [SimBrief Integration](simbrief.md)                       |
-| [Throttle Calibration](flypados3/throttle-calibration.md) |
+| [Throttle Calibration](flypados3/throttle-calibration.md) |
+| [flyPadOS 3 EFB](flypados3/index.md)                      |
+
+
+

docs/fbw-a32nx/feature-guides/simbrief.md

@@ -6,11 +6,9 @@ title: SimBrief Integration
 
 # SimBrief and Navigraph Integration
 
-Please use the Quick Links to jump to any relevant section. For connecting your SimBrief/Navigraph Accounts, click the relevant button below.
+Please use the Quick Links to jump to any relevant section. For connecting your SimBrief/Navigraph Accounts, click the button below.
 
-[Development Version - Link Navigraph/SimBrief](#setup-a32nx-simbrief-integration){.md-button}
-
-[Stable Version - Link Navigraph/SimBrief](#stable-version-only){.md-button}
+[Setup SimBrief/Navigraph](#setup-a32nx-simbrief-integration){.md-button}
 
 ## Quick Links
 
@@ -80,27 +78,6 @@ If successful, you should see your account name followed by your Navigraph accou
 
 If you are still unsure of where the Settings page on the EFB is, please see [flyPad Settings](flypados3/settings.md).
 
-??? warning "Stable Version Only"
-    ### Stable Version Only    
-
-    The SimBrief username needs to be configured in the flyPad EFB under Settings -> ATSU/AOC. [Location Here](flypados3/settings.md##atsuaoc).
-
-    Before you can use the A32NX simBrief Integration, you need to provide your simBrief account details.
-
-    - SimBrief Pilot ID:
-
-        - Enter your SimBrief Pilot ID into the applicable field
-
-          ![simBrief Account field](../assets/flypados3/simbrief-account-field.png "simBrief Account field")
-
-        - If you entered a wrong Pilot ID, a red error message will be displayed.
-
-          ![simBrief Account Field Error](../assets/flypados3/simbrief-account-field-error.png "simBrief Account Field Error")
-
-    To get your simBrief Pilot ID, you can go to your simBrief Account settings and open "SimBrief Data".
-
-    ![simBrief Account Data](../assets/flypados3/simbrief-account-data.png "simBrief Account Data")
-
 ## Using the flyPad SimBrief Integration
 
 ### Importing the SimBrief OFP to the flyPad

docs/pilots-corner/advanced-guides/flight-guidance/vertical-guidance/managed-modes.md

@@ -29,8 +29,6 @@ The SRS guidance law also includes:
 
 ## CLB (Climb)
 
-!!! warning "Managed CLB or DES (VNAV) is currently only available in the Development Version."
-
 CLB mode guides the aircraft in a managed climb, at either a managed or a selected target speed, to an FCU selected altitude, considering altitude constraints at waypoints. The system also considers speed constraints if the target speed is managed.
 
 The AP/FD pitch controls the speed or Mach number target and the A/THR is in thrust mode (CLB) corresponding to maximum climb thrust. The flight path may include several segments. The flight crew can arm the CLB mode during the takeoff, go-around, climb, and cruise phases and engage it during the climb and cruise phases.
@@ -88,8 +86,6 @@ When ALT is engaged, the FMA displays ALT in green (FCU altitude hold), ALT CST
 
 ## DES (Descent)
 
-!!! warning "Managed CLB or DES (VNAV) is currently only available in the Development Version."
-
 The managed descent mode guides the aircraft along the FMS computed vertical flight path. The DES mode is preferred when conditions permit, since it ensures the management of altitude constraints and reduces the operating cost when flying at ECON DES speed.
 
 The DES mode is only available when the aircraft flies on the FMS lateral flight plan, i.e., when the aircraft uses the NAV horizontal guidance mode.

docs/pilots-corner/beginner-guide/descent.md

@@ -206,7 +206,7 @@ For more information on the different types of minimums, see the [Minimums and M
 
     - Search online for the real life D-ATIS at your arrival airport (much like the ATIS example above).
     - Use the `Trans ALT` + 1000 ft.
-        - **Development Version:** If you have imported your flight plan via our simBrief integration, this value would be autopopulated for you.  
+    - If you have imported your flight plan via our simBrief integration, this value would be autopopulated for you.
 
 ![Transition level on chart](../assets/beginner-guide/descent/EGKK-APPR-char-1.png "Transition level on chart"){loading=lazy}<br/>
 ![ILS information on chart](../assets/beginner-guide/descent/EGKK-APPR-chart-2.png "ILS information on chart"){loading=lazy}<br/>
@@ -250,8 +250,6 @@ A few minutes before we reach our calculated descent point (TOD) we request clea
 !!! info "TOD marker A320"
     The A320 has a downward pointing arrow at the TOD to support the pilot with the decision of when to descend. Ultimately, it is still the pilot's responsibility to calculate and validate the TOD.
 
-    The TOD (top of descent) marker on the `ND` is available in the Development Version. 
-
 When clearance is given, we can start our descent to the flight level or altitude ATC has given us.
 
 For descending, we set the new flight level or altitude in the `FCU` with the `altitude selector`. We can then either PUSH the selector for `Managed Altitude Mode` (constraints are respected, also known as [DES](../advanced-guides/flight-guidance/vertical-guidance/managed-modes.md#des-descent)) or PULL the selector for `Selected Altitude Mode` (constraints are ignored, also known as [OP DES](../advanced-guides/flight-guidance/vertical-guidance/selected-modes.md#op-des-open-descent)). 
@@ -273,13 +271,9 @@ ATC typically will not clear us to our final target altitude directly, but will
 
 Also, ATC will often still expect us to respect the STAR's constraints, although they might have given us a lower clearance. We should then only descent to the constraint's altitude.
 
-<!-- TODO: update when vertical nav is available -->
 !!! info "VNAV in the FlyByWire A32NX"
     The scenario that we are cleared to a lower altitude or flight level with altitude constraints above the clearance is an ideal scenario for the called so "VNAV" autopilot mode, which would be activated by using "`Managed Altitude Mode`" (pushing the `ALT selector`). The autopilot will automatically level off at the constraint and continue descending when the constraint is no longer valid.
 
-    !!! warning ""
-        VNAV is currently only supported in our Development Version of the A32NX.
-
 We repeat the process until we have reached our desired final approach altitude.
 
 !!! info "Airline SOPs"
@@ -298,10 +292,6 @@ We repeat the process until we have reached our desired final approach altitude.
     - Check that the /LS/GLS identification is displayed on the PFD.
 - `RAD NAVAIDS` (`RNAV` page on MCDU): Selected/Identified
     - Ensure that appropriate radio NAVAIDS are tuned and identified. The A32NX is capable of autotuning to the correct frequency.
-
-        !!! warning "Autotuning"
-            Not available in the Stable Version of the A32NX.
-
     - For NDB approaches, manually select the reference NAVAID.
 
 #### Approach Checklist

docs/pilots-corner/beginner-guide/engine-start-taxi.md

@@ -206,10 +206,6 @@ Perform the AFTER START checklist.
 
         The FlyByWire checklist's trim section at the bottom indicates we would need to set a nose up trim of about 0.2.
 
-    !!! warning "The CG scale available in the Asobo model of the flight deck is not entirely accurate for the A320neo. This is corrected in the [Development Version](https://docs.flybywiresim.com/fbw-a32nx/fbw-versions/#development-version-recommended) of the Plane."
-
-
-
 ---
 
 ## Flight Controls Check

docs/pilots-corner/beginner-guide/landing.md

@@ -87,7 +87,7 @@ To intercept the ILS Localizer, we follow these steps:
     ![ILS lateral deviation marker moving inwards](../assets/beginner-guide/landing/PFD-ILS-deviation-scale.png "ILS lateral deviation marker moving inwards"){loading=lazy}
 
 ??? note "What is the blue-dashed line?"
-    You might ask what the blue dashed line is. It is part of the new FIX INFO feature, available only in the Development version for the time being. It allows drawing distance rings or radial lines from navigation fixes. For this illustration, it helps us to visualize the localizer signal path at 261° into the runway, which we are going to capture with the APPR mode.
+    You might ask what the blue dashed line is. It is part of the FIX INFO feature which allows drawing distance rings or radial lines from navigation fixes. For this illustration, it helps us to visualize the localizer signal path at 261° into the runway, which we are going to capture with the APPR mode.
 
 !!! warning "Arming APPR"
     Using `APPR` also arms the glideslope descent (G/S) and the aircraft will descend as soon as it captures the ILS glideslope signal.

docs/pilots-corner/beginner-guide/preflight.md

@@ -21,7 +21,7 @@ You can choose to use other software/websites to plan your route, but when using
     - [Little Nav Map](https://albar965.github.io/littlenavmap.html){target=new} (Flight Planning and Charts)
     - [ChartFox](https://chartfox.org/){target=new} (Charts)
     - [Navigraph](https://navigraph.com/){target=new} (Flight Planning and Charts) <span style="color:red;">**Requires Subscription**</span>
-    - See our [Custom Flight Management System](../../fbw-a32nx/feature-guides/cFMS.md) page and the [special notes section](../../fbw-a32nx/feature-guides/cFMS.md#special-notes) when using our development version of the aircraft.
+    - See our [Custom Flight Management System](../../fbw-a32nx/feature-guides/cFMS.md) page and the [special notes section](../../fbw-a32nx/feature-guides/cFMS.md#special-notes) section.
 
 ## Flight Plan Import
 

docs/pilots-corner/beginner-guide/preparing-mcdu.md

@@ -366,9 +366,6 @@ On this page, we can input our zero fuel weight (ZFW) and zero fuel weight cente
 
     *Ideally you no longer have to wait for boarding to be completed to finalize preparations on the INIT FUEL PRED page.*
 
-    ??? info "Open for Stable Version Only"
-        Fuel and payload have to be set in the aircraft (see link below) and passenger boarding has to be **complete** for the ZFW/ZFWCG to be correct.
-
     Gross Weight (GW) value on the ECAM will appear only when certain conditions are satisfied:
 
     - This page (INIT FUEL PRED) has a ZFW/ZFWCG value. **Reminder:** After engines are started, INIT FUEL PRED changes to the FUEL PRED page.