Update deploying.md (#1665)

encoredev · Dec 20, 2024 · 5b7c86d · 5b7c86d
1 parent 9d2df3a
commit 5b7c86d
Show file tree

Hide file tree

Showing 2 changed files with 4 additions and 4 deletions.
diff --git a/docs/platform/deploy/deploying.md b/docs/platform/deploy/deploying.md
@@ -10,7 +10,7 @@ Encore Cloud simplifies deploying your application, making it as simple as pushi
 
 ## Deploying your application
 
-### Step 1: Pre-requisites
+### Step 1: Prerequisites
 
 Before deploying, ensure that you have an **Encore Cloud account** and have created an **Encore application**.
 
@@ -40,7 +40,7 @@ Once connected to GitHub, pushing code will trigger deployments automatically. E
 
 ### Step 3: Connect your AWS / GCP account (Optional)
 
-Deploy to your own cloud on AWS or GCP by connection your cloud account to Encore Cloud.
+Deploy to your own cloud on AWS or GCP by connecting your cloud account to Encore Cloud.
 
 If you're just trying out Encore Cloud, skip this step to deploy to a free development environment using Encore Cloud's hosting, subject to [fair use limits](/docs/platform/management/usage).
 

diff --git a/docs/platform/deploy/environments.md b/docs/platform/deploy/environments.md
@@ -33,7 +33,7 @@ Environment type is also used for [Secrets management](/docs/ts/primitives/secre
 2. Go to **Environments** > **Create env**
 3. Configure your environment:
    - Name your environment
-   - Choose type: **Production** or **Development** (see [Environment Types](#environment-types) below)
+   - Choose type: **Production** or **Development** (see [Environment Types](#environment-types))
    - Set deploy trigger: Git branch or manual
    - Configure infrastructure approval: automatic or manual
    - Select cloud provider
@@ -49,7 +49,7 @@ To configure which branch name is used to trigger deploys, open your app in the
 
 ### Configuring infrastructure approval
 
-For environments you may want to enforce infrastructure approval before deploying. You can configure this in the **Settings** > **Infrastructure Approval** section for your environment.
+For some environments you may want to enforce infrastructure approval before deploying. You can configure this in the **Settings** > **Infrastructure Approval** section for your environment.
 
 When infrastructure approval is enabled, an application **Admin** will need to manually approve the infrastructure changes before the deployment can proceed.