diff --git a/action-layout.Rmd b/action-layout.Rmd
index cca38165..c0b1c05c 100644
--- a/action-layout.Rmd
+++ b/action-layout.Rmd
@@ -53,7 +53,7 @@ fluidPage(
 )
 ```
 
-Even though you haven't these functions yet, you can guess what's going on by reading their names.
+Even though you haven't learned these functions yet, you can guess what's going on by reading their names.
 You might imagine that this code will generate a classic app design: a title bar at top, followed by a sidebar (containing a slider) and main panel (containing a plot).
 The ability to easily see hierarchy through indentation is one of the reasons it's a good idea to use a consistent style.
 
@@ -512,7 +512,7 @@ ui <- fluidPage(
 )
 ```
 
-If you're a HTML/CSS expert, you might be interested to know that can skip `fluidPage()` altogether and supply raw HTML.
+If you're a HTML/CSS expert, you might be interested to know that you can skip `fluidPage()` altogether and supply raw HTML.
 See "[Build your entire UI with HTML](https://shiny.rstudio.com/articles/html-ui.html)" for more details.
 
 Alternatively, you can use of the HTML helper that Shiny provides.
diff --git a/action-workflow.Rmd b/action-workflow.Rmd
index e26ed0fb..2c09340b 100644
--- a/action-workflow.Rmd
+++ b/action-workflow.Rmd
@@ -346,7 +346,7 @@ server <- function(input, output, session) {
 
 I thought, *it's an eight line app, what could possibly go wrong?* Well, when I opened the app up I saw a **lot** of missing values, no matter what territory I selected.
 The code most likely to be the source of the problem was the reactive that selected the data to show: `sales[sales$TERRITORY == input$territory, ]`.
-So stopped the app, and quickly verified that subsetting worked the way I thought it did:
+So I stopped the app, and quickly verified that subsetting worked the way I thought it did:
 
 ```{r}
 sales[sales$TERRITORY == "EMEA", ]