diff --git a/_posts/2018/05/2018-05-13-reticulate.md b/_posts/2018/05/2018-05-13-reticulate.md
index 77f50c20d..9c867389d 100644
--- a/_posts/2018/05/2018-05-13-reticulate.md
+++ b/_posts/2018/05/2018-05-13-reticulate.md
@@ -15,19 +15,19 @@ you might know that I will be facilitating two sessions:
 and
 "Bring and Build Your Own Lesson 'Carpentries-style'" on Friday, 1 June.
 During the process to organise both sessions,
-I have being thinking a lot of what we could improve
+I have ben thinking a lot of what we could improve
 in the way that we write our lessons.
 One of the things that I know that annoys many of the maintainers
-is the fact that they need to copy and past the output of each command.
+is the fact that they need to copy and paste the output of each command.
 RStudio has been work in a new project called [reticulate](https://rstudio.github.io/reticulate/)
-to "enables easy interoperabilty between Python and R chunks"
-and in this process they made much easier to use Python from R Markdown.
+that "enables easy interoperabilty between Python and R chunks"
+and in this process they have made it much easier to use Python from R Markdown.
 
 I created [one pull request to swcarpentry/lesson-example](https://github.com/swcarpentry/lesson-example/pull/202)
-with an concept idea of using reticulate.
+with an concept idea of using `reticulate`.
 The pull request includes some screenshots
-of Bash and Python code chucks being processed by R Markdown.
-This is one discussion that all members of the community are welcome to participate,
+of Bash and Python code chunks being processed by R Markdown.
+This is one discussion that all members of the community are welcome to participate in,
 so please leave a comment on the pull request
 or, even better, find me during CarpentryCon to talk about it,
-if you are what promice to be a great conference.
+if you are at what promises to be a great conference.