Update importacao.md

bohr-io · Dec 11, 2023 · 08e9e12 · 08e9e12
1 parent 2afaaa4
commit 08e9e12
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/i18n/en/docusaurus-plugin-content-docs/current/importacao.md b/i18n/en/docusaurus-plugin-content-docs/current/importacao.md
@@ -12,7 +12,7 @@ Only the repositories to which you have granted access permission will be listed
 
 For example, in a React project repository, bohr.io will identify from the `package.json` that the framework used is **React** and that the folder containing the content is `build`. With this information, bohr.io will generate the publication.
 
-When you click "**Import**", you will need to wait a few seconds while the **Overview** screen loads the simulation. In the GitHub repository, you can see that bohr.io will make a commit adding a **GitHub Actions** workflow file, used to build the project (you can track this execution in the Actions tab on GitHub).
+When you click "**Import**", you must wait a few seconds while the **Overview** screen loads the simulation. In the GitHub repository, bohr.io will commit to adding a **GitHub Actions** workflow file used to build the project (you can track this execution in the **Actions** tab on GitHub).
 
 The repository will install the bohr.io CLI and perform the publication, attempting to identify the framework. Depending on the framework you are using, you may need to make some additional configurations within the site's **Settings** (if you encounter any issues, feel free to reach out to us on [Discord](https://discord.com/invite/p3hhfGg2Uy)).
 
@@ -22,7 +22,7 @@ After the compilation and upload are complete, a publication URL is generated.
 
 
 :::note
-Due to a small delay on the **Overview** screen, your project's preview may initially return a "Site not Found" message. Don't worry; simply refresh the screen.
+Due to a slight delay on the **Overview** screen, your project's preview may initially return a "Site not Found" message. Don't worry; just refresh the screen.
 :::
 
 In the **Settings** screen, under **Environment Variables**, you can see the variables being used during execution. They can be modified in case of any issues or if they are not detected (if needed, reach out to us on [Discord](https://discord.com/invite/p3hhfGg2Uy)).