Fixes MicrosoftDocs/azure-docs#116928

Target and source are swapped in this document. Updated the words to ensure accuracy.

Author: BryanTrach-MSFT

articles/app-service/deploy-staging-slots.md

@@ -96,14 +96,14 @@ The slot's URL has the format `http://sitename-slotname.azurewebsites.net`. To k
 
 When you swap two slots (usually from a staging slot into the production slot), App Service does the following to ensure that the target slot doesn't experience downtime:
 
-1. Apply the following settings from the target slot (for example, the production slot) to all instances of the source slot: 
+1. Apply the following settings from the source slot (for example, the production slot) to all instances of the target slot: 
     - [Slot-specific](#which-settings-are-swapped) app settings and connection strings, if applicable.
     - [Continuous deployment](deploy-continuous-deployment.md) settings, if enabled.
     - [App Service authentication](overview-authentication-authorization.md) settings, if enabled.
 
-    Any of these cases trigger all instances in the source slot to restart. During [swap with preview](#Multi-Phase), this marks the end of the first phase. The swap operation is paused, and you can validate that the source slot works correctly with the target slot's settings.
+    Any of these cases trigger all instances in the target slot to restart. During [swap with preview](#Multi-Phase), this marks the end of the first phase. The swap operation is paused, and you can validate that the source slot works correctly with the target slot's settings.
 
-1. Wait for every instance in the target slot to complete its restart. If any instance fails to restart, the swap operation reverts all changes to the source slot and stops the operation.
+1. Wait for every instance in the source slot to complete its restart. If any instance fails to restart, the swap operation reverts all changes to the source slot and stops the operation.
 
 1. If [local cache](overview-local-cache.md) is enabled, trigger local cache initialization by making an HTTP request to the application root ("/") on each instance of the source slot. Wait until each instance returns any HTTP response. Local cache initialization causes another restart on each instance.