diff --git a/%5BRFC%5D-Development-%26-Deployment-Process-for-Brotherton.md b/%5BRFC%5D-Development-%26-Deployment-Process-for-Brotherton.md
index 2b71a59..edf12a1 100644
--- a/%5BRFC%5D-Development-%26-Deployment-Process-for-Brotherton.md
+++ b/%5BRFC%5D-Development-%26-Deployment-Process-for-Brotherton.md
@@ -9,7 +9,7 @@ Sometimes, client-specific changes will need to be made in the source code if th
 
 Each developer should have their own accounts in staging and prod, so that changes can be tracked back to the developer for accountability. All changes made by "Administrator" can be assumed to have been done by Landry. Going forward, the Administrator account should only be used for provisioning other accounts.
 
-Before we switch to this new process, we should backup the prod database and apply it to staging, so that they start in the same place. Then, as long as we make custom changes to staging first, staging should always be equal to or ahead of prod.
+Before we switch to this new process, we should backup the prod database and restore it to staging, so that they start in the same place. Then, as long as we make custom changes to staging first, staging should always be equal to or ahead of prod.
 
 
 ### Building custom images