Update articles/operational-excellence/relocation-functions.md

Co-authored-by: Glenn Gailey <[email protected]>

Author: anaharris-ms

articles/operational-excellence/relocation-functions.md

@@ -63,7 +63,7 @@ This section is a planning checklist in the following areas:
 
 - **Determine whether your Functions App is stateful or stateless.**  Although its recommended that Functions (With the exception of Durable Functions) be stateless, and the files on the `%HOME%\site` drive should be only those required to run the deployed application and any temporary files, it's possible to store runtime application state on the `%HOME%\site` virtual drive. If your application writes state on the app shared storage path, make sure to plan how you are going to manage that state during a resource move.
 
-If the application uses Durable Functions, and particularly Durable Entities, the migration becomes much more application centric, and depends on the needs of the application itself. You must consider how to migrate entity state and how to reconcile the new entity state with the old service. This is particularly the case, if you are doing anything more complex than a straight Active/Active + GRS Failover.
+When your application uses Durable Functions, and particularly Durable Entities, the migration becomes much more application centric, and depends on the needs of the application itself. You must consider how to migrate entity state and how to reconcile the new entity state with the old service. This is particularly the case, when you are doing anything more complex than a straight Active/Active + GRS Failover.
 
 ### Certificates