Merge pull request #262805 from RyanHill-MSFT/issues/118555-slot-clarity

(Azure CXP) update deploy-staging-slots

Author: prmerger-automator[bot]

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

@@ -94,14 +94,14 @@ The slot's URL has the format `http://sitename-slotname.azurewebsites.net`. To k
 
 ### Swap operation steps
 
-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:
+When you swap two slots (usually from a staging slot *as the source* into the production slot *as the target*), App Service does the following to ensure that the target slot doesn't experience downtime:
 
-1. Apply the following settings from the source slot (for example, the production slot) to all instances of the target slot: 
+1. Apply the following settings from the target slot (for example, the production slot) to all instances of the source 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 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.
+    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.
 
 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.