Merge pull request #680 from N1TJ/patch-1

Update 2.1-runway-selection-and-pushback.md

atc-manual/2.-ground/2.1-runway-selection-and-pushback.md

@@ -41,17 +41,19 @@ Controllers **must**{.red} check that the area is clear before issuing pushback
 
 > By looking at the strips; the oldest "hold position" command would have been sent to the bottom of the tab providing useful reference as to who requested pushback first
 
-
-
-### 2.1.4    
+### 2.1.4   
 
 Under most circumstances, the Controller **should**{.red} approve an aircraft’s initial request to pushback or taxi, regardless of aircraft type or parking, due to the availability of pushback equipment for all aircraft and the wide variety of parking spot configurations.
 
 > Controllers **should**{.red} be familiar with their airport’s parking configuration while operating. i.e. can aircraft pull straight through their remote stand? Do aircraft require a pushback to safely exit the spot?
 
+### 2.1.5
+
+Auto pushback and/or tail position assignment **should**{.red} be used to the max extent possible at eligible airports to dictate the pushback path and beginning taxi position of aircraft under your control. To pause an auto pushback in progress, advise the aircraft to “hold position”. A subsequent “pushback approved” is approval to resume the previously assigned auto pushback. When a conflict is not present controller **may**{.red} elect to approve a pushback without tail or auto push guidance.
 
+>  To amend a pushback path controllers should advise the aircraft to hold position and reissue a new pushback clearance with the amended path.
 
-### 2.1.5    
+### 2.1.6    
 
-The use of "expect runway xx" **should**{.red} be used if the Controller deems it necessary for the aircraft to face a particular direction for pushback (to promote efficiency); however, it is not required for each pushback clearance.
+The use of "expect runway xx" **may**{.red} be used if the Controller deems it necessary; however, it is not required for each pushback clearance.