Various error corrections

docs/pilots/atc/clearances.md

@@ -36,7 +36,7 @@ dateCreated: 2020-09-11T03:45:45.724Z
 <p>A pilot should call up the Oceanic Controller first to establish initial contact and to make the controller aware that the pilot is looking to request their oceanic clearance.&nbsp;</p>
 <blockquote>
   <p><strong>BAW123: </strong>Gander Radio, BAW123, request oceanic clearance.</p>
-  <p><strong>CZQX_FSS</strong>: BAW123, Gander Radio, pass your message</p>
+  <p><strong>CZQO_CTR</strong>: BAW123, Gander Radio, pass your message</p>
 </blockquote>
 <p>Once the Oceanic Controller has given the “pass your message” or “go ahead” instruction, BAW123 may now request their oceanic clearance. In the request, the following must be included:</p>
 <ul>
@@ -53,15 +53,15 @@ dateCreated: 2020-09-11T03:45:45.724Z
 <p>The controller will acknowledge the pilot's request and will tell BAW123 to standby.&nbsp;</p>
 <p>When the controller is ready, the clearance is issued:</p>
 <blockquote>
-  <p><strong>CZQX_FSS</strong>: Gander Oceanic clears BAW123 London Heathrow via ALLRY, track Alpha. From ALLRY maintain Flight Level 350, Mach .80</p>
+  <p><strong>CZQO_CTR</strong>: Gander Oceanic clears BAW123 London Heathrow via ALLRY, track Alpha. From ALLRY maintain Flight Level 350, Mach .80</p>
 </blockquote>
 <p>BAW123 must, in the readback of their clearance, confirm that their version of the NAT track message is up-to-date by including the TMI (see <a href="https://knowledgebase.ganderoceanic.com/en/basics/nats">North Atlantic Tracks</a>):</p>
 <blockquote>
   <p><strong>BAW123: </strong>BAW123 is cleared to London Heathrow, via NAT track Alpha, TMI 115. From ALLRY maintain Flight Level 350, Mach .80</p>
 </blockquote>
 <p>When BAW123 has made a correct readback, the controller will confirm that the readback was correct and will instruct the pilot to “return to domestic frequency” or to “return to previous frequency”.&nbsp;</p>
 <blockquote>
-  <p><strong>CZQX_FSS: </strong>BAW123, read-back correct, return to previous frequency.</p>
+  <p><strong>CZQO_CTR: </strong>BAW123, read-back correct, return to previous frequency.</p>
 </blockquote>
 <p>For aircraft requesting random routings through Shanwick/Gander OCAthe whole random routing must be included in the request, including all coordinates and the entry/exit fixes. Pilots are additionally required to read back the full route issued by the controller. ‘Cleared as filed’ is not an available phrase.</p>
 <p>Below are some more possible examples.</p>
@@ -71,23 +71,23 @@ dateCreated: 2020-09-11T03:45:45.724Z
 ### Clearance flying via a NAT track
 <blockquote>
   <p><strong>ACA865:</strong> Shanwick Radio, ACA865 request oceanic clearance.</p>
-  <p><strong>EGGX_FSS: </strong>ACA865, Shanwick Radio, pass your message</p>
+  <p><strong>EGGX_CTR: </strong>ACA865, Shanwick Radio, pass your message</p>
   <p><strong>ACA865:</strong>&nbsp;ACA865 request clearance via Track Bravo. Estimating PIKIL at 1131. Request Mach .80, Flight Level 350, able Flight Level 360.</p>
-  <p><strong>EGGX_FSS:&nbsp;</strong>Shanwick Oceanic clears ACA865 to Toronto via PIKIL, track Bravo, from PIKIL maintain Flight Level 350, Mach .80</p>
+  <p><strong>EGGX_CTR:&nbsp;</strong>Shanwick Oceanic clears ACA865 to Toronto via PIKIL, track Bravo, from PIKIL maintain Flight Level 350, Mach .80</p>
   <p><strong>ACA865:</strong>&nbsp;ACA865 is cleared to Toronto via PIKIL, track Bravo, from PIKIL maintain Flight Level 350, Mach .80</p>
-  <p><strong>EGGX_FSS:&nbsp;</strong>ACA865, read-back correct</p>
+  <p><strong>EGGX_CTR:&nbsp;</strong>ACA865, read-back correct</p>
 </blockquote>
 <p>(<strong>Note:</strong> coordinates shall be spoken as "five four north, zero two zero west". Times shall be spoken as "one one three one", and not "eleven thirty-one")</p>
 
 ### Clearance flying via Random Routing
 <p>Sometimes you may be flying on a "random route" instead of a NAT tracks. It's more or less the same as above, except that you need to read the full route instead of "Track A".</p>
 <blockquote>
   <p><strong>ACA865:</strong> Shanwick Radio, ACA865 request oceanic clearance.</p>
-  <p><strong>EGGX_FSS: </strong>ACA865, Shanwick Radio, pass your message</p>
+  <p><strong>EGGX_CTR: </strong>ACA865, Shanwick Radio, pass your message</p>
   <p><strong>ACA865:</strong>&nbsp;ACA865 request oceanic clearance via MALOT 54N020W 56N030W 57N040W 56N050W JANJO. Estimating MALOT at 1131. Request Mach .80, Flight Level 350, able Flight Level 360</p>
-  <p><strong>EGGX_FSS:&nbsp;</strong>Shanwick Oceanic clears ACA865 to Toronto via MALOT 54N020W 56N030W 57N040W 56N050W JANJO, from MALOT maintain Flight Level 350, Mach .80</p>
+  <p><strong>EGGX_CTR:&nbsp;</strong>Shanwick Oceanic clears ACA865 to Toronto via MALOT 54N020W 56N030W 57N040W 56N050W JANJO, from MALOT maintain Flight Level 350, Mach .80</p>
   <p><strong>ACA865:</strong>&nbsp;ACA865 is cleared to Toronto via MALOT 54N020W 56N030W 57N040W 56N050W JANJO, from MALOT maintain Flight Level 350, Mach .80</p>
-  <p><strong>EGGX_FSS:&nbsp;</strong>ACA865, read-back correct</p>
+  <p><strong>EGGX_CTR:&nbsp;</strong>ACA865, read-back correct</p>
 </blockquote>
 <p>(<strong>Note:</strong> coordinates shall be spoken as "5 4 north 0 2 0 west". Times shall be spoken as "1 1 3 1", and not "eleven thirty-one")</p>
 <p><strong>Note: a full read-back of the clearance is always required.</strong></p>
@@ -96,19 +96,19 @@ dateCreated: 2020-09-11T03:45:45.724Z
 <p>Sometimes it is not possible for a controller to issue the requested clearance. There are four main types of amendments: reroute, level change, speed change and entry point change.</p>
 <blockquote>
   <p><strong>ACA865:</strong> Shanwick Radio, ACA865 request oceanic clearance.</p>
-  <p><strong>EGGX_FSS: </strong>ACA865, Shanwick Radio, pass your message</p>
+  <p><strong>EGGX_CTR: </strong>ACA865, Shanwick Radio, pass your message</p>
   <p><strong>ACA865:</strong>&nbsp;ACA865 request clearance via Track Bravo. Estimating PIKIL at 1131. Request Mach .80, Flight Level 350, able Flight Level 360</p>
-  <p><strong>EGGX_FSS:&nbsp;</strong>ACA865, Oceanic Clearance with a <strong>level change</strong>, Shanwick Oceanic clears ACA865 to Toronto via PIKIL, track Bravo, from PIKIL maintain Flight Level 330, Mach .80. Unable requested level.</p>
+  <p><strong>EGGX_CTR:&nbsp;</strong>ACA865, Oceanic Clearance with a <strong>level change</strong>, Shanwick Oceanic clears ACA865 to Toronto via PIKIL, track Bravo, from PIKIL maintain Flight Level 330, Mach .80. Unable requested level.</p>
   <p><strong>ACA865:</strong>&nbsp;ACA865 is cleared to Toronto via PIKIL, track Bravo, from PIKIL maintain Flight Level 330, Mach .80</p>
-  <p><strong>EGGX_FSS:&nbsp;</strong>ACA865, read-back correct</p>
+  <p><strong>EGGX_CTR:&nbsp;</strong>ACA865, read-back correct</p>
 </blockquote>
 <p>A controller may sometimes include multiple amendments in the same clearance:</p>
 <blockquote>
-  <p><strong>EGGX_FSS:&nbsp;</strong>ACA865, Oceanic Clearance with a <strong>level change and speed change</strong>, Shanwick Oceanic clears ACA865 to Toronto via PIKIL, track Bravo, from PIKIL maintain Flight Level 330, Mach .81. Unable requested level, unable requested speed.</p>
+  <p><strong>EGGX_CTR:&nbsp;</strong>ACA865, Oceanic Clearance with a <strong>level change and speed change</strong>, Shanwick Oceanic clears ACA865 to Toronto via PIKIL, track Bravo, from PIKIL maintain Flight Level 330, Mach .81. Unable requested level, unable requested speed.</p>
 </blockquote>
 <p>A controller may also, on occasion, request a pilot to cross a point at/before/after a certain time:</p>
 <blockquote>
-  <p><strong>EGGX_FSS:&nbsp;</strong>Shanwick Oceanic clears ACA865 to Toronto via PIKIL, track Bravo, from PIKIL maintain Flight Level 330, Mach .81. Cross PIKIL at or after time 1135.</p>
+  <p><strong>EGGX_CTR:&nbsp;</strong>Shanwick Oceanic clears ACA865 to Toronto via PIKIL, track Bravo, from PIKIL maintain Flight Level 330, Mach .81. Cross PIKIL at or after time 1135.</p>
 </blockquote>
 
 ## Sources

docs/pilots/atc/pos-reps.md

@@ -39,13 +39,13 @@ dateCreated: 2020-09-11T03:46:30.382Z
   <p><strong>SWR100:</strong> Shanwick Radio, Swissair 100 with position report</p>
 </blockquote>
 <blockquote>
-  <p><strong>EGGX_FSS: </strong>Swissair 100, Shanwick Radio, pass your message</p>
+  <p><strong>EGGX_CTR: </strong>Swissair 100, Shanwick Radio, pass your message</p>
 </blockquote>
 <blockquote>
   <p><strong>SWR100: </strong>Shanwick Radio, Swissair 100 reports passing RESNO at time 1235, Flight Level 330, estimating 56 North 020 West at 1310, 56 North 030 West next</p>
 </blockquote>
 <blockquote>
-  <p><strong>EGGX_FSS: </strong>Swissair 100, Shanwick copies Swissair 100 passed RESNO time 1235, Flight Level 330, estimating 56 North 020 West at time 1310, 56 North 030 West next</p>
+  <p><strong>EGGX_CTR: </strong>Swissair 100, Shanwick copies Swissair 100 passed RESNO time 1235, Flight Level 330, estimating 56 North 020 West at time 1310, 56 North 030 West next</p>
 </blockquote>
 <blockquote>
   <p><strong>SWR100:</strong> Shanwick Radio, Swissair 100, correct.</p>
@@ -55,13 +55,13 @@ dateCreated: 2020-09-11T03:46:30.382Z
   <p><strong>BAW212:</strong> Shanwick Radio, Speedbird 212 with revised estimate</p>
 </blockquote>
 <blockquote>
-  <p><strong>EGGX_FSS: </strong>Speedbird 212, Shanwick Radio, pass your message</p>
+  <p><strong>EGGX_CTR: </strong>Speedbird 212, Shanwick Radio, pass your message</p>
 </blockquote>
 <blockquote>
   <p><strong>BAW212:</strong> Shanwick Radio, Speedbird 212 estimating 57 North 040 West at 0305</p>
 </blockquote>
 <blockquote>
-  <p><strong>EGGX_FSS: </strong>Speedbird 212, Shanwick Radio copies revision 57 North 040 West at time 0305</p>
+  <p><strong>EGGX_CTR: </strong>Speedbird 212, Shanwick Radio copies revision 57 North 040 West at time 0305</p>
 </blockquote>
 <blockquote>
   <p><strong>BAW212:</strong> Shanwick Radio, Speedbird 212</p>

docs/pilots/atc/revisions.md

@@ -22,15 +22,15 @@ dateCreated: 2020-09-11T03:47:25.963Z
   <p><strong>BAW123:</strong> Shanwick Radio, Speedbird 123 requesting a re-route after 57/20 via 58/15, GOMUP, GINGA.</p>
 </blockquote>
 <blockquote>
-  <p><strong>EGGX_FSS:</strong> Speedbird 123, amended route clearance, Shanwick re-clears Speedbird 123 after 57/20 to re-route via 58/15, GOMUP, GINGA.</p>
+  <p><strong>EGGX_CTR:</strong> Speedbird 123, amended route clearance, Shanwick re-clears Speedbird 123 after 57/20 to re-route via 58/15, GOMUP, GINGA.</p>
 </blockquote>
 <p><strong>Meaning:</strong> The pilot shall follow their previous route until reaching 57/20, whereby they are cleared to re-route direct 58/15, GOMUP and GINGA.</p>
 <p><strong>Level clearance - no restrictions:</strong></p>
 <blockquote>
   <p><strong>ACA123: </strong>Gander Radio, Air Canada 123, requesting climb to FL340.</p>
 </blockquote>
 <blockquote>
-  <p><strong>CZQX_FSS:</strong> Gander Radio clears ACA123, climb FL340.</p>
+  <p><strong>CZQO_CTR:</strong> Gander Radio clears ACA123, climb FL340.</p>
 </blockquote>
 <p>Sometimes, the controller may ask the pilot to report when leaving their current flight level, and/or when reaching their cleared flight level. In this case, the pilot should report when they have commenced their climb/descent, or when they have reached their cleared level.</p>
 <blockquote>
@@ -41,20 +41,20 @@ dateCreated: 2020-09-11T03:47:25.963Z
   <p><strong>ACA123:</strong> Air Canada 123, requesting climb to FL340.</p>
 </blockquote>
 <blockquote>
-  <p><strong>CZQX_FSS:</strong> Gander Radio clears ACA123, climb FL340 to be level at or before 2048z. Report leaving, report reaching.</p>
+  <p><strong>CZQO_CTR:</strong> Gander Radio clears ACA123, climb FL340 to be level at or before 2048z. Report leaving, report reaching.</p>
 </blockquote>
 <p><strong>Meaning:</strong> The pilot is cleared to climb to FL340, but must do so before 2048z. They must report leaving their current flight level, and report reaching the new flight level.</p>
 <p><strong>Speed clearance - no restrictions:</strong></p>
 <blockquote>
   <p><strong>BAW123:</strong> Speedbird 123, requesting increase Mach .89.</p>
 </blockquote>
 <blockquote>
-  <p><strong>EGGX_FSS:</strong> Speedbird 123, Shanwick clears Speedbird 123 increase Mach .89.</p>
+  <p><strong>EGGX_CTR:</strong> Speedbird 123, Shanwick clears Speedbird 123 increase Mach .89.</p>
 </blockquote>
 <p><strong>Meaning:</strong> The pilot is cleared to increase their speed to Mach .89.</p>
 <p><strong>Speed clearance - with restriction:</strong><br>Just like level clearances, controllers sometimes need to issue restrictions with the speed revision. These are usually a combination of geographically and time-based instructions. It is unusual for a pilot to ask for speed clearances in this way, and as such, it is nearly always controller-initiated.</p>
 <blockquote>
-  <p><strong>EGGX_FSS:</strong> Speedbird 123, amended speed clearance, Shanwick clears Speedbird 123 cross 52/20 at or before 1623z.</p>
+  <p><strong>EGGX_CTR:</strong> Speedbird 123, amended speed clearance, Shanwick clears Speedbird 123 cross 52/20 at or before 1623z.</p>
 </blockquote>
 <p><strong>Meaning:</strong> The pilot shall adjust their speed accordingly to reach 52/20 before 1623z. It is then assumed that the pilot will resume the Mach number they received in their clearance thereafter.&nbsp;</p>
 <p>All of the above exchanges regularly occur without the pilot initiating the request. More often than not, the controller needs to make an amendment without the pilot specifically asking for the change. This is the ‘controller instruction’ method.</p>

docs/pilots/atc/selcal.md

@@ -24,7 +24,7 @@ dateCreated: 2020-09-11T03:44:47.128Z
   <p><strong>ACA123</strong>: Gander Radio, Air Canada 123 request SELCAL check on FS-BQ (Foxrot Sierra Bravo Quebec)</p>
 </blockquote>
 <blockquote>
-  <p><strong>CZQX_FSS</strong>: Air Canada 123, Gander Radio, stand by for SELCAL check.</p>
+  <p><strong>CZQO_CTR</strong>: Air Canada 123, Gander Radio, stand by for SELCAL check.</p>
 </blockquote>
 
 ## Sources

docs/pilots/basics/airspace.md

@@ -27,7 +27,7 @@ dateCreated: 2020-09-11T03:37:30.150Z
   <li><strong>Reykjavik</strong>: control over Greenland up to FL195 (Llt-Red)</li>
   <li><strong>Gander Oceanic Transition Area (delegated to Gander Domestic)</strong>: west of 50 degrees west (yellow)</li>
   <li><strong>Gander Domestic</strong>: above FL55 bounded by CARPE, LOGSU, VODOR, 45/50 and 50/50 (dark-red)</li>
-  <li><strong>New York: </strong>Control in the airspace 44.5/50, 45/50, 45/40, 44.5/40</li>
+  <li><strong>New York</strong>: Control in the airspace 44.5/50, 45/50, 45/40, 44.5/40</li>
 </ul>
 
 ### Shanwick OCA

docs/pilots/basics/first-principles.md

@@ -9,7 +9,7 @@ editor: undefined
 dateCreated: 2020-09-11T03:36:14.212Z
 -->
 
-# First prinicples 
+# First principles 
 
 ## Flying over the North Atlantic
 

docs/pilots/nattrak/receiving-your-clearance.md

@@ -38,11 +38,11 @@ The datalink format is as follows:
 * `KLM621 CLRD TO KATL VIA NEBIN` You're cleared to KATL via NEBIN, your entry waypoint.
 * `NAT E` your NAT track/random routeing.
 * `NEBIN 54/20 55/30 55/40 53/50 PELTU` The track routeing.
-* `FM NEBIN/1837 MNTN F350 M085` From PIKIL (estimating arrival at 10:33Z), maintain FL350, mach .83.
+* `FM NEBIN/1837 MNTN F350 M085` From NEBIN (estimating arrival at 10:33Z), maintain FL350, mach .83.
 
 > **NOTE:** Changes from your initial request will appear with a ```/``` infront of them. Examples can be found in the above image. A reclearance will always appear with one change, so make sure to take note of what the new restriction is.
 
-The voice format below that represents the usual voice formats as per [Getting Your Clearance](/atc/clearances).
+The voice format below that represents the usual voice formats as per [Getting Your Clearance](../atc/clearances.md).
 
 
 ## Acknowleding your clearance and reverting to voice