Skip to content

Commit b9eeeeb

Browse files
authored
fix(descent): remove fix info dev flags and correct grammar
1 parent f0b2aa5 commit b9eeeeb

File tree

1 file changed

+5
-7
lines changed

1 file changed

+5
-7
lines changed

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

Lines changed: 5 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -104,14 +104,14 @@ This guide will cover these phases:
104104

105105
![ND distance rings](../assets/beginner-guide/descent/ND-disctance-rings.png "ND distance rings"){loading=lazy width=45% align=right}
106106

107-
??? tip "FIX INFO in Development Version"
108-
##### Fix Info Distance Ring
107+
??? tip "FIX INFO"
108+
##### FIX INFO Distance Ring
109109

110-
Also, a great aid for knowing when to descend is the new FIX INFO feature available in the Development Version.
110+
A great aid for knowing when to descend is the FIX INFO feature.
111111

112112
You can add a ring around a waypoint or fix with a specified distance. As we need 57NM for our descent from FL320 to FL140 at ABTUM we can set the fix distance ring to 57NM.
113113

114-
Now we can easily see or TOD (top of descent) on the ND.
114+
Now we can easily see our TOD (top of descent) on the ND.
115115

116116
!!! block ""
117117

@@ -121,9 +121,7 @@ This guide will cover these phases:
121121

122122
The MCDU FIX INFO page can be accessed by selecting the first waypoint on the F-PLN page and pressing LSK 1L "FIX INFO".
123123

124-
See our feature guide [Fix Info](../advanced-guides/flight-planning/fixinfo.md) for how to use this function.
125-
126-
!!! warning "Available in the Development version!"
124+
See our feature guide [FIX INFO](../advanced-guides/flight-planning/fixinfo.md) for how to use this function.
127125

128126
#### How to Calculate the Required Distance for Descent
129127

0 commit comments

Comments
 (0)