Fixed formatting issue with ATC examples and warnings

docs/aerodrome/muscat/air.md

@@ -19,18 +19,18 @@ Runway 08L/26R features three departure points per configuration. The standard d
 Conditional line up instructions shall include the traffic that the aircraft is to follow, as well as the word “behind” at the beginning and end of the transmission. It is recommended to only have a maximum of two conditional line up clearances active at once.
 
 !!! example
-  **Controller:** "SWR243, behind the departing Oman Air A330, runway 26R line upand wait behind."
+    **Controller:** "SWR243, behind the departing Oman Air A330, runway 26R line upand wait behind."
 
 If aircraft have not yet reached the holding point where they are expected to line up at, ATC shall reiterate the cleared holding point.
 
 !!! example
-  **Controller:** "OMA298 via Y7, line up and wait runway 26R"
+    **Controller:** "OMA298 via Y7, line up and wait runway 26R"
 
 ### 4.3.3 Take-off clearances
 Aircraft shall be cleared for take-off once adequate separation exists, as provided in 4.3.4.
 
 !!! example
-  **Controller:** "OMA8KC, wind 280 degrees 4 knots, runway 26R cleared for take-off."
+    **Controller:** "OMA8KC, wind 280 degrees 4 knots, runway 26R cleared for take-off."
 
 ### 4.3.4 Separation requirements
 #### 4.3.4.1 General
@@ -55,12 +55,12 @@ Aircraft that have commenced their take-off roll may be instructed to stop immed
 It must be noted though, that the instruction to stop must be given early enough such that the aircraft does not reach its decision speed. The stopping distance of an aircraft is also significant. Therefore, aerodrome controllers must be vigilant and remain aware of the location of traffic at all times as well as runway incursion hotspots.
 
 !!! example
-  **Controller:** "FDB687, Stop immediately, I say again stop immediately, runway incursion."
+    **Controller:** "FDB687, Stop immediately, I say again stop immediately, runway incursion."
 
 For aircraft that have been given a take-off clearance, but have not yet started the roll, they shall be instructed to hold position and the take-off clearance must be cancelled along with the reason.
 
 !!! example
-  **Controller:** "FDB687, hold position, cancel takeoff clearance, I say again cancel takeoff clearance, aircraft entering the runway."
+    **Controller:** "FDB687, hold position, cancel takeoff clearance, I say again cancel takeoff clearance, aircraft entering the runway."
 
 ## 4.4 Arrival Procedures
 ### 4.4.1 Preferred exit points
@@ -74,7 +74,7 @@ While the radar controllers are responsible for separating and sequencing arrivi
 If it is apparent that minimum separation may not exist, TWR may use a tactical reduction in aircraft speed.
 
 !!! example
-  **Controller:** "OMA1784, reduce to final approach speed."
+    **Controller:** "OMA1784, reduce to final approach speed."
 
 #### 4.4.2.3 Visual separation
 Aircraft may be instructed to maintain own separation visually, if speed control alone will not resolve the conflict. This shall only be done in VMD and in agreement with the pilot. If no other solutions are practical, the succeeding aircraft shall be instructed to go around.
@@ -84,20 +84,20 @@ Aircraft may be instructed to maintain own separation visually, if speed control
 Should a runway at any time become unsuitable for an aircraft landing, or separation minima is not met, aircraft shall be instructed to go-around. 
 
 !!! example
-  **Controller:** "UAE797, go around, I say again, go around. Acknowledge."
+    **Controller:** "UAE797, go around, I say again, go around. Acknowledge."
 
 At Muscat, instructions in case of a go-around are usually assigned by Muscat Approach. However, Muscat Tower may reiterate these if necessary and if these change, after coordination with Muscat Radar. Once aircraft have acknowledged the instruction and are observed to be safely climbing away, they shall be transferred to Muscat TMA.
 
 !!! example
-  **Controller:** "UAE797, (fly runway heading, climb to altitude 3,000ft,) contact Muscat Radar 121.200."
+    **Controller:** "UAE797, (fly runway heading, climb to altitude 3,000ft,) contact Muscat Radar 121.200."
 
 ### 4.4.4 Arrival taxi procedures
 In accordance with taxi procedures laid down in 3.4, aircraft shall be provided an intial taxi clearance to ensure they are kept moving, such that the relevant rapid exit taxiway (RET) is kept clear for the next arrival.
 
 The intiial taxi instruction shall include instructions to taxi "LEFT" or "RIGHT" onto the relevant taxiway, as appropriate, and a hold short instruction at a suitable intermediate holding point.
 
 !!! example
-  **Controller:** "OMA8KC, taxi right on W, hold short of V"
+    **Controller:** "OMA8KC, taxi right on W, hold short of V"
 
 Once aircraft have been observed to be taxiing and completely clear of the RET, transfer of control shall be initiated to GMC, provided there will be no conflicts with other traffic.
 
@@ -113,7 +113,7 @@ If aircraft are exiting into uncontrolled airspace, they shall be instructed to
 TWR control is responsible for managing circuit traffic. Circuits will always be conducted to the north of the airfield. Once aircraft are ready for departure they shall be cleared for take-off in sequence. As they begin their crosswind turn, they shall be instructed to report when they are on downwind with their intentions
 
 !!! example
-  **Controller:** "A-TT, report downwind with intentions"
+    **Controller:** "A-TT, report downwind with intentions"
 
 Aircraft may request a touch and go, a stop and go, a low approach or a full stop landing. Once TWR is aware of the aircraft’s request, they may be sequenced to the runway, with due consideration given to runway occupancy time.
 
@@ -122,20 +122,22 @@ Aircraft on downwind shall be passed the following information:
 • Traffic information if applicable
 
 !!! example
-  **Controller:** "A-TT, number 1, report final runway 26R."
-  **Controller:** "A-TT, runway 30R, cleared to land/touch and go/low approach."
+    **Controller:** "A-TT, number 1, report final runway 26R."
+
+    **Controller:** "A-TT, runway 30R, cleared to land/touch and go/low approach."
 
 ### 4.5.3 VFR arrivals
 Inbound VFR aircraft shall be instructed to contact TWR with enough time such that two-way radio communication has been established before aircraft enter the control zone. On first contact TWR will pass instructions on how to enter the CTR, the runway in use and the QNH.
 
 !!! example
-  **Controller:** “A4O-TT, Muscat Tower, Enter control zone via Cement Plant East, Runway 26R, 2,000 feet VFR, QNH 1017”
+    **Controller:** “A4O-TT, Muscat Tower, Enter control zone via Cement Plant East, Runway 26R, 2,000 feet VFR, QNH 1017”
 
 Once the traffic is closer to the aerodrome, they shall be given circuit joining instructions. VFR arrivals from the south can either be given a direct base for the respective runway or if there is a delay expected they should make a midfield crossing to join the normal circuit in the north of the aerodrome.
 
 !!! example
-  **Controller:** "A-TT, join base runway 26R" or
-  **Controller:** "A-TT, cross midfield, join right-hand downwind runway 26R"
+    **Controller:** "A-TT, join base runway 26R" or
+
+    **Controller:** "A-TT, cross midfield, join right-hand downwind runway 26R"
 
 VFR arrivals may be denied entry into the control zone during times of increased IFR arrival activity and instructed to hold outside controller airspace awaiting further instructions. VFR aircraft may also be told to orbit at any VRP inside the CTR.
 

docs/aerodrome/muscat/gmc.md

@@ -11,12 +11,12 @@ Aircraft requesting push that are not squawking their assigned transponder code
 Pushback direction is based primarily on aircraft location and runway configuration. Pushback from the main terminal shall occur onto T or L as appropriate. A pushback clearance must be a variant of those provided in 3.2.2 and include an instruction on which direction to face (e.g. “FACE WEST”).
 
 !!! example
-  **Controller:** "OMA613, Muscat Ground, Pushback Approved, Face West on T."
+    **Controller:** "OMA613, Muscat Ground, Pushback Approved, Face West on T."
 
 Conditional pushback instructions may also be issued if an aircraft is taxiing behind another, waiting for pushback.
 
 !!! example
-  **Controller:** "FDB3EF, Behind Oman Air A320 passing left to right, pushback approved, face east on T behind."
+    **Controller:** "FDB3EF, Behind Oman Air A320 passing left to right, pushback approved, face east on T behind."
 
 ### 3.2.2 Pushback direction
 When departing runway 26R, aircraft parked on the north side of the main terminal (stands 2xx and 3xx) shall be instructed to "FACE EAST" or "FACE NORTH", accordingly.
@@ -33,7 +33,7 @@ This type will normally have the aircraft stop abeam the adjacent stand. The phr
 A short pushback instruction shall require the aircraft to complete the pushback abeam the current stand such that the adjacent stand will not be blocked.
 
 !!! example 
-  **Controller:** "OMA51, short pushback approved, face West on L, to finish abeam stand 406."
+    **Controller:** "OMA51, short pushback approved, face West on L, to finish abeam stand 406."
 
 ### 3.2.4 Simultaneous pushback operations
 Simultaneous pushbacks may be permitted from adjacent stands provided aircraft are instructed to manoeuver in accordance with 3.2.2 such that on completion of both aircraft’s pushback operation, they will be separated on the taxiway by two aircraft stands.
@@ -52,7 +52,7 @@ Taxiway N is used for southbound aircraft, while taxiway R is used for northboun
 Traffic south of runway 08R/26L shall exit their apron at the respective apron exit, then taxi via A to cross runway 08R/26L at intersection D1, then continue via E1, H, etc. 
 
 !!! warning
-  Controllers shall exercise caution when taxiing aircraft to/from the aprons south of runway 08R/26L, as only a single intersection connects the apron to the rest of the aerodrome, increasing the risk of a nose-nose situation. 
+    Controllers shall exercise caution when taxiing aircraft to/from the aprons south of runway 08R/26L, as only a single intersection connects the apron to the rest of the aerodrome, increasing the risk of a nose-nose situation. 
 
 Taxiway V shall be used by departing aircraft in all configurations.
 
@@ -61,10 +61,10 @@ These directions keep traffic flow organised and reduces the potential for confl
 To deconflict traffic and to reduce the length of taxi clearances, intermediate holding points shall be used wherever possible. 
 
 !!! example
-  **Controller:** "OMA7R, Taxi via T, UE, V, holding point Y7 runway 26R"
+    **Controller:** "OMA7R, Taxi via T, UE, V, holding point Y7 runway 26R"
 
 !!! example
-  **Controller:** "OMA7R, Taxi via T, hold UE"
+    **Controller:** "OMA7R, Taxi via T, hold UE"
 
 ## 3.4 Arrival taxi procedures
 ### 3.4.1 General arrival taxi procedures

docs/aerodrome/muscat/gmp.md

@@ -34,8 +34,11 @@ An IFR clearance shall be in the following format:
 
 !!! example
     **Pilot**: "Muscat Delivery, OMA478, Boeing 777-300ER, information X, stand 215, request clearance to Dubai."
+
     **Controller**: "OMA478, Muscat Delivery, information X correct, cleared to Dubai via T508 SOLUD, ITLAK1N departure, maintain altitude 3000ft, squawk 2613."
+
     **Pilot**: "Cleared to Dubai via T508 SOLUD, ITLAK1N departure, maintain altitude 3000ft, squawk 2613, OMA478."
+
     **Controller**: "OMA478, readback correct, QNH 1016, report ready for pushback."
 
 ## 2.4 Aircraft routing