Admonition Changes

docs/aerodromes/classc/Adelaide.md

@@ -44,21 +44,21 @@ The TCU controller will coordinate these aircraft with ADC prior to issuing airw
   <figcaption>Clearance Limits (red) and Approach/Departure Path (green)</figcaption>
 </figure>
 
-!!! example
+!!! phraseology
     *CNY is a VFR Cessna 172 tracking coastal northbound, approaching PNL. They have contacted AD TCU for clearance.*    
     <span class="hotline">**TCU** -> **ADC**</span>: "South of PNL, CNY, for coastal northbound, 500ft, clearance limit BTJ"  
     <span class="hotline">**ADC** -> **TCU**</span>: "CNY"
 
 If a delay is expected at the clearance limit, instruct the aircraft to hold there.
 
-!!! example 
+!!! phraseology 
     **CNY:** "Adelaide Tower, CNY, maintaining not above 500ft"  
     **AD ADC:** "CNY, Adelaide Tower, hold at the clearance limit, expect onwards clearance in 5 minutes due inbound traffic"  
     **CNY:** "Hold at the clearance limit, CNY"  
 
 Once the conflict is no longer a threat (or if no holding was required in the first place), cancel the clearance limit and issue onwards clearance tracking coastal north/southbound at the desired level.
 
-!!! example 
+!!! phraseology 
     **AD ADC:** "CNY, cancel clearance limit, track coastal offshore northbound, not above 500ft"  
     **CNY:** "Cancel clearance limit, track coastal offshore northbound, not above 500ft, CNY"
 
@@ -111,7 +111,7 @@ Shall be assigned the **Radar SID**.
 
 All other aircraft require a 'Next' call to AD TCU.
 
-!!! example
+!!! phraseology
     <span class="hotline">**AD ADC** -> **AD TCU**</span>: "Next, RXA4362, Runway 23"  
     <span class="hotline">**AD TCU** -> **AD ADC**</span>: "RXA4362, Track Extended Centreline, Unrestricted"  
     <span class="hotline">**AD ADC** -> **AD TCU**</span>: "Track Extended Centreline, RXA4362"  

docs/aerodromes/classc/Amberley.md

@@ -31,11 +31,11 @@ Visual Departures are commonly requested by high performance military jets and o
 
 Aircraft will depart the circuit visually and track overhead YAMB to begin tracking for their initial waypoint.
 
-!!! example
+!!! phraseology
     CRNG21 plans to enter R637 via the gate MOSSI for Military Training.
     **AMB ADC**: "CRNG21, cleared to YAMB via MOSSI, flight planned route. Runway 15, Northern 1 Departure. Climb to `F190`. Squawk 3601, Departure Frequency 126.20"  
 
-!!! example
+!!! phraseology
     WOLF03 was assiged the BYRON7 departure with their initial clearance. 
     **AMB ADC**: "WOLF03, make left turn, reach `F190` by COWIE, cleared for takeoff"  
     **WOLF03**: "Make left turn, reach `F190` by COWIE, cleared for takeoff, WOLF03"  
@@ -77,7 +77,7 @@ The Circuit Area Airspace is allocated to be within 5nm of the YAMB ARP from `SF
 
 'Next' coordination is required from AMB ADC to AMB TCU for all aircraft.
 
-!!! example
+!!! phraseology
     <span class="hotline">**AMB ADC** -> **AMB TCU**</span>: "Next, ASY01, runway 33"  
     <span class="hotline">**AMB TCU** -> **AMB ADC**</span>: "ASY01, Assigned Heading Right 030, unrestricted"  
     <span class="hotline">**AMB ADC** -> **AMB TCU**</span>: "Assigned Heading Heading Right 030, ASY01"  

docs/aerodromes/classc/Brisbane.md

@@ -70,7 +70,7 @@ Winds must always be considered for Runway modes (Crosswind <20kts, Tailwind <5k
 
 When using the SODPROPS mode, pass traffic information to aircraft that are departing and landing at the same time
 
-!!! example
+!!! phraseology
     **BN ADC:** "ABC, Traffic is DEF, a 737, on short final for the opposite direction parallel runway. Runway 01R, Cleared for Takeoff"  
     **ABC:** "Cleared for Takeoff Runway 01R, ABC"  
     **BN ADC:** "DEF, Traffic is ABC, an A320, departing from the opposite direction parallel runway to the South-West. Runway 19R, Cleared to Land"  
@@ -134,7 +134,7 @@ The ATIS shall always have `EXP INST APCH` as the approach type. Visual Approach
 
 All other aircraft require a 'Next' call to BN TCU.
 
-!!! example
+!!! phraseology
     <span class="hotline">**BN ADC** -> **BN TCU**</span>: "Next, QLK404D, Runway 19L"  
     <span class="hotline">**BN TCU** -> **BN ADC**</span>: "QLK404D, heading 160, unrestricted"  
     <span class="hotline">**BN ADC** -> **BN TCU**</span>: "Heading 160, QLK404D"   

docs/aerodromes/classc/Cairns.md

@@ -15,7 +15,7 @@
 ## Airspace
 CS ADC is responsible for the Class C airspace within the CS CTR `SFC` to `A010`.
 
-!!! important
+!!! warning "Important"
     CS ADC is responsible for issuing visual approach clearances to some aircraft tracking for runway 33 in CTA, as well as initial airways clearances for VFR aircraft entering the CTR from class G. See [Runway 33 Arrival Procedures](#runway-33) for more information.
 
 <figure markdown>
@@ -46,7 +46,7 @@ When visual approaches are in use, expect light & medium category aircraft (B737
 
 ADC must assess any potential conflicts with aircraft in the CTR and clear the inbound aircraft for a visual approach when able. Given the limited airspace available, it is crucial that ADC maintains separation assurance between inbound aircraft and those operating in the CTR, to avoid a delay in issuing the visual approach clearance.
 
-!!! example 
+!!! phraseology 
     <span class="hotline">**TCU** -> **ADC**</span>: "Via right base, RXA5418, will be assigned A020 visual"  
     <span class="hotline">**ADC** -> **TCU**</span>: "A020 visual, RXA5418"  
 
@@ -82,7 +82,7 @@ Prior to issuing clearance to these helicopters, ensure that no conflict exists
 
 Arriving helicopters should be cleared direct to The Pier, not above `A005` and instructed to report on the ground.
 
-!!! example
+!!! phraseology
     *YZM is a VFR R44 tracking from Upolo Cay to False Cape, inbound to The Pier.*  
     **VH-YZM**: "Cairns Tower, helicopter YZM, 5nm northeast of False Cape, A005, for The Pier, received Hotel"  
     **CS ADC**: "YZM, Cairns Tower, cleared direct to The Pier, not above A005, report on the ground"  
@@ -93,7 +93,7 @@ Arriving helicopters should be cleared direct to The Pier, not above `A005` and
 
 Departing helicopters should be cleared direct to their nominated tracking point not above `A005`, and instructed to report airborne.
 
-!!! example
+!!! phraseology
     *VTB is a VFR Bell 505 on The Pier, intending to track to Cairns Airport for a landing on the southern pads. A 737 is about to depart from runway 15.*  
     **VH-VTB**: "Cairns Tower, helicopter VTB, at The Pier, for the southern pads, received India"  
     **CS ADC**: "VTB, Cairns Tower, short delay for clearance"  
@@ -112,20 +112,20 @@ Departing helicopters should be cleared direct to their nominated tracking point
 ### Western VFR Corridor
 The Western VFR Corridor conflicts with the extended centreline to the north of the aerodrome. Clearances for aircraft entering the CTR must use clear and unambiguous phraseology to eliminate any potential for confusion by the pilot.
 
-!!! Example
+!!! phraseology
     **NDR**: "Cairns Tower, NDR, EDT, A015, for the Western VFR Corridor, Request Clearance"  
     **CS ADC**: "NDR, enter the CTR tracking via the Western VFR corridor at A015. Remain on the corridor until advised."
 
 If a clearance limit is associated with the clearance, then it must be reiterated to the pilot to remain “on or west of the VFR Corridor”.
 
-!!! Example
+!!! phraseology
     **NDR**: "Cairns Tower, NDR, EDT, A015, for the Western VFR Corridor, Request Clearance"  
     **CS ADC**: "NDR, enter the CTR tracking via the Western VFR Corridor at A015. Clearance limit is ADI, Remain on or west of the Western VFR Corridor at all times."
 
 ### Inbound
 Aircraft planning to enter the CS CTR between *Mt Gorton*, CGF and Upolo Cay at `A005`, must contact CS ADC for airways clearance.
 
-!!! Example
+!!! phraseology
     **NDR**: "Cairns Tower, NDR, Cape Grafton, A005, Inbound, Information Alpha, Request Clearance"  
     **CS ADC**: "NDR, enter the CTR tracking for a Right Base runway 33, maintain A005."
 
@@ -164,7 +164,7 @@ Taxiways A2 and A between A2 and A3 are not available to aircraft above 7,000 ki
 
 All other aircraft require a 'Next' call to CS TCU.
 
-!!! example
+!!! phraseology
     <span class="hotline">**CS ADC** -> **CS TCU**</span>: "Next, HND151"  
     <span class="hotline">**CS TCU** -> **CS ADC**</span>: "HND151, Heading 030, unrestricted"  
     <span class="hotline">**CS ADC** -> **CS TCU**</span>: "Heading 030, HND151"   
@@ -182,7 +182,7 @@ The controller assuming responsibility of **CS ACD** shall give heads-up coordin
 a) VFR Departures  
 b) Aircraft using a runway not on the ATIS
 
-!!! example
+!!! phraseology
     <span class="coldline">**CS ACD** -> **CS TCU**</span>: "ABC, Requesting clearance for a Northbound VFR Coastal departure at A035"  
     <span class="coldline">**CS TCU** -> **CS ACD**</span>: "ABC, Cleared for a Northbound VFR Coastal departure, A035"  
     <span class="coldline">**CS ACD** -> **CS TCU**</span>: "Cleared for a Northbound VFR Coastal departure, A035, ABC"   

docs/aerodromes/classc/Canberra.md

@@ -39,7 +39,7 @@ VFR aircraft that will operate only in ADCs airspace shall be assigned SSR code
 
 Aircraft operating in the circuit area are to remain on the ADC frequency. The phrasing of the airways clearance is:
 
-!!! example
+!!! phraseology
     “ABC, cleared to operate in the circuit area, not above A030, squawk 0040”.
 
 The circuit direction is not specified in the airways clearance, but with a take-off or touch-and-go clearance.
@@ -67,13 +67,13 @@ Helicopters departing the pads require an airways clearance to do so, either tak
 
 Departing aircraft should **not** be issued a takeoff clearance (as the helipads are outside the manoeuvring area). Instead, instruct aircraft to 'report airborne'.
 
-!!! example
+!!! phraseology
     *RSCU201 is a VFR AW139 helicopter intending to depart Southcare Base (YXSB) to the northwest at `A035` (below the base of the Class C steps).*  
     **RSCU201**: "Canberra Tower, helicopter RSCU201, Southcase Base, for departure to the northwest, A035, received Juliet, ready"  
     **CB ADC**: "RSCU201, Canberra Tower, transit approved not above A035, report OCTA"  
     **RSCU201**: "Transit approved, not above A035, RSCU201"
 
-!!! example
+!!! phraseology
     *RSCU209 is an IFR AW139 helicopter intending to depart Canberra Hospital (YXCB) for Bankstown (YSBK) at `A090` (inside Class C CTA).*  
     **RSCU209**: "Canberra Tower, helicopter RSCU209, on the pad at Canberra Hospital, for Bankstown, received Juliet, ready"  
     **CB ADC**: "RSCU209, Canberra Tower, report sighting a Jetstar A320 on a 3nm final runway 35 and advise able to maintain own separation with that aircraft"  
@@ -87,7 +87,7 @@ Departing aircraft should **not** be issued a takeoff clearance (as the helipads
 #### Arriving Aircraft
 Helicopters arriving to the pads will generally be coordinated by the TMA controller and should be cleared via a visual approach (when available) and instructed to report on the ground. Do **not** issue a landing clearance to these aircraft (as the helipads are outside the manoeuvring area). It may be necessary to instruct these helicopters to track via amended visual points or sight and pass other aircraft.
 
-!!! example
+!!! phraseology
     **RSCU203**: "Canberra Tower, gday, RSCU203"  
     **CB ADC**: "RSCU203, Canberra Tower, report sighting a Qantas 737 lining up on runway 17 and advise able to maintain own separation with that aircraft"  
     **RSCU203**: "Traffic sighted and affirm, RSCU203"  
@@ -106,7 +106,7 @@ Helicopters arriving to the pads will generally be coordinated by the TMA contro
 
 All other aircraft require a 'Next' call to CB TCU.
 
-!!! example
+!!! phraseology
     <span class="hotline">**CB ADC** -> **CB TCU**</span>: "Next, XEB, runway 35"  
     <span class="hotline">**CB TCU** -> **CB ADC**</span>: "XEB, heading 010, Unrestricted"  
     <span class="hotline">**CB ADC** -> **CB TCU**</span>: "Heading 010, XEB"

docs/aerodromes/classc/Curtin.md

@@ -27,7 +27,7 @@ CIN ADC owns the Class C airspace within the CIN MIL CTR from `SFC` to `A015`.
 ### CIN TCU
 'Next' coordination is required from CIN ADC to CIN TCU for all aircraft.
 
-!!! example
+!!! phraseology
     <span class="hotline">**CIN ADC** -> **CIN TCU**</span>: "Next, ASY404, runway 29"  
     <span class="hotline">**CIN TCU** -> **CIN ADC**</span>: "ASY404, unrestricted"  
     <span class="hotline">**CIN ADC** -> **CIN TCU**</span>: "ASY404"  

docs/aerodromes/classc/Darwin.md

@@ -88,7 +88,7 @@ Assign VFR routes in accordance with the following radial chart:
 ### DN TCU
 Auto-Release is **not available** at YPDN. All Departures will be coordinated when ready for departure.
 
-!!! example
+!!! phraseology
     <span class="hotline">**DN ADC** -> **DN TCU**</span>: "Next, EOC, runway 18"  
     <span class="hotline">**DN TCU** -> **DN ADC**</span>: "EOC, Track Extended Centreline, unrestricted"  
     <span class="hotline">**DN ADC** -> **DN TCU**</span>: "Track Extended Centreline, EOC"  

docs/aerodromes/classc/EastSale.md

@@ -127,7 +127,7 @@ Lanes are defined by GNSS waypoints situated at 12, 35, and 50 NM from YMES AD.
 
 Aircraft departing ESL military airspace may be instructed to track via a lane at or below `F160`.
 
-!!! example
+!!! phraseology
     **BRCT21** is departing East Sale via the Eastern Lane at FL110 to Orbost (YORB). The departure clearance would be issued as follows:
     **ES SMC** -> **BRCT21**: "BRCT21 CLEARED TO YORB, VIA EASTERN LANE, FPR, FL110, SQUAWK 1234, DEPARTURES 123.3"
 
@@ -142,14 +142,14 @@ Aircraft departing ESL military airspace may be instructed to track via a lane a
 ### Auto Release
 Auto release is not utilised at East Sale. 'Next' coordination is required from ES ADC to ES TCU for all aircraft.
 
-!!! example
+!!! phraseology
     <span class="hotline">**ES ADC** -> **ES TCU**</span>: "Next, ASY01, runway 09"  
     <span class="hotline">**ES TCU** -> **ES ADC**</span>: "ASY01, Assigned Heading Left 030, unrestricted"  
     <span class="hotline">**ES ADC** -> **ES TCU**</span>: "Left Heading 030, ASY01" 
 
 Helicopters departing from helicopter spots will be treated as if departing from the duty runway.
 
-!!! example
+!!! phraseology
     *PSDN14 is a VFR helicopter departing from the threshold of RWY04 (in the direction of runway 27)*  
     <span class="hotline">**ES ADC** -> **ES TCU**</span>: "Next, PSDN14, runway 27"  
     <span class="hotline">**ES TCU** -> **ES ADC**</span>: "PSDN14, right turn, unrestricted"  

docs/aerodromes/classc/Essendon.md

@@ -92,7 +92,7 @@ EN ADC is responsible for facilitating aircraft requesting city orbits. They sha
 `A015` by day  
 `A022` by night
 
-!!! example
+!!! phraseology
     **EOG**: "Essendon Tower, EOG, approaching WMS, A015, Requesting 1 left-hand city orbit, in receipt of L"  
     **EN ADC**: "EOG, Essendon Tower, cleared 1 left-hand city orbit A015"  
     **EOG**: "Cleared 1 left-hand city orbit A015, EOG"  
@@ -113,7 +113,7 @@ Essendon departures that will not enter ML TCU Class C airspace are not required
 
 All aircraft departing into Class C must be coordinated to ML TCU with a "Next" Call
 
-!!! example
+!!! phraseology
     <span class="hotline">**EN ADC** -> **ML TCU**</span>: "Next, FD318"  
     <span class="hotline">**ML TCU** -> **EN ADC**</span>: "FD318, heading 330, unrestricted"  
     <span class="hotline">**EN ADC** -> **ML TCU**</span>: "Heading 330, FD318"
@@ -125,7 +125,7 @@ ML TCU will heads-up coordinate arrivals/overfliers from Class C to EN ADC.
 IFR aircraft will be cleared for the coordinated approach (Instrument or Visual) prior to handoff to EN ADC, unless EN ADC nominates a restriction.  
 VFR aircraft require a level readback.
 
-!!! example 
+!!! phraseology 
     <span class="hotline">**ML TCU** -> **EN ADC**</span>: "via KAO, KHU"  
     <span class="hotline">**EN ADC** -> **ML TCU**</span>: "KHU, A015"
 
@@ -140,7 +140,7 @@ Any Runway change must be prior coordinated to **ML TCU**
 ### ML ADC
 EN ADC is responsible for separation with all YMML traffic, and must coordinate any aircraft operating in EN ADC airspace that cannot be visually or laterally separated with the 09/27 or 16/34 Extended Centrelines at YMML.
 
-!!! example 
+!!! phraseology 
     <span class="hotline">**EN ADC** -> **ML ADC**</span>: "Boundary Ident, OXG, Published Missed Approach from the ILS 26"  
     <span class="hotline">**ML ADC** -> **EN ADC**</span>: "OXG, My restriction is QFA451 on a 10nm final RWY 34. Your separation"  
     <span class="hotline">**EN ADC** -> **ML ADC**</span>: "My separation with QFA451, OXG"

docs/aerodromes/classc/Goldy.md

@@ -88,7 +88,7 @@ Circuits from the Western Grass are to be made in the same direction as the duty
 
 All other aircraft require a 'Next' call to CG TCU.
 
-!!! example
+!!! phraseology
     <span class="hotline">**CG ADC** -> **BAC**</span>: "Next, CBN, runway 14"  
     <span class="hotline">**BAC** -> **CG ADC**</span>: "CBN, heading 030, unrestricted"  
     <span class="hotline">**CG ADC** -> **BAC**</span>: "Heading 030, CBN"  

docs/aerodromes/classc/Learmonth.md

@@ -26,7 +26,7 @@ LM ADC owns the Class C airspace within the LM CTR from `SFC` to `A015`.
 ### LM TCU
 'Next' coordination is required from LM ADC to LM TCU for all aircraft.
 
-!!! example
+!!! phraseology
     <span class="hotline">**LM ADC** -> **LM TCU**</span>: "Next, QFA1601, runway 36"  
     <span class="hotline">**LM TCU** -> **LM ADC**</span>: "QFA1601, Right heading 060 Visual, unrestricted"  
     <span class="hotline">**LM ADC** -> **LM TCU**</span>: "Right heading 060 Visual, QFA1601"