diff --git a/docs/3.0.0-beta.x/migration-guide/migration-guide-beta.18-to-beta.19.md b/docs/3.0.0-beta.x/migration-guide/migration-guide-beta.18-to-beta.19.md
index 67ff1589a4..339ce8da15 100644
--- a/docs/3.0.0-beta.x/migration-guide/migration-guide-beta.18-to-beta.19.md
+++ b/docs/3.0.0-beta.x/migration-guide/migration-guide-beta.18-to-beta.19.md
@@ -44,11 +44,11 @@ We decided to change the policies naming convention to match with the future nam
 - Global policy: `global::{policy}`.
 - Plugin policy: `plugins::{pluginName}.{policy}`.
 
-We are also introductin application naming so you can access an api policy easily or reference it absolutely when the context doesn't allow forto find out directly.
+We are also introducing application naming so you can access an api policy more easily or reference it absolutely when the context otherwise wouldn't allow to find it directly.
 
 You can now reference a policy located at `./api/{apiName}/config/policies/{policy}` with the following syntax: `{apiName}.{policy}`.
 
-Although we do not recommend it (error prone), you can still access a local policy with the syntax `{policy}` . This syntax will only allow access to a policy declared in the api you are referencing it from. (e.g, polici in `restaurant` api and route in `restaurant` api only).
+Although we do not recommend it (as it is error prone), you can still access a local policy with the syntax `{policy}` . This syntax will only allow access to a policy declared in the api you are referencing it from. (e.g, a policy in the `restaurant` api and a route in the `restaurant` api only).
 
 ## Rebuilding your administration panel