diff --git a/workshop/content/java/buildpipe/pipeascode/deploy/_index.en.md b/workshop/content/java/buildpipe/pipeascode/deploy/_index.en.md
index 1c68afe..f62bee1 100755
--- a/workshop/content/java/buildpipe/pipeascode/deploy/_index.en.md
+++ b/workshop/content/java/buildpipe/pipeascode/deploy/_index.en.md
@@ -4,7 +4,7 @@ date = 2019-10-04T12:54:48-07:00
 weight = 40
 +++
 
-The **Deploy Stage** is where your SAM application and all its resources are created an in an AWS account. The most common way to do this is by using CloudFormation ChangeSets to deploy. This means that this stage will have 2 actions: the _CreateChangeSet_ and the _ExecuteChangeSet_.
+The **Deploy Stage** is where your SAM application and all its resources are created in an AWS account. The most common way to do this is by using CloudFormation ChangeSets to deploy. This means that this stage will have 2 actions: the _CreateChangeSet_ and the _ExecuteChangeSet_.
 
 Add the Deploy stage to your PipelineStack.java: 
 
@@ -148,4 +148,4 @@ The CLI might ask you to confirm the changes before deploying, this is because w
 
 Navigate to your pipeline and you will see the Deploy stage has been added, however, it is currently grayed out because it hasn't been triggered. Let's just trigger a new run of the pipeline manually by clicking the Release Change buttton. 
 
-![ReleaseChange](/images/chapter4/screenshot-release-change.png)
\ No newline at end of file
+![ReleaseChange](/images/chapter4/screenshot-release-change.png)