diff --git a/content/blaze/step04.md b/content/blaze/step04.md
index dc7a291..8a546ab 100644
--- a/content/blaze/step04.md
+++ b/content/blaze/step04.md
@@ -14,6 +14,8 @@ Here's the JavaScript code we need to add to listen to the `submit` event on the
 
 Now your app has a new input field. To add a task, just type into the input field and hit enter. If you open a new browser window and open the app again, you'll see that the list is automatically synchronized between all clients.
 
+*Note: In newer versions of meteor you will need to run ```meteor add insecure``` in the console in order to allow the client write access to the tasks collection on the server.
+
 ### Attaching events to templates
 
 Event listeners are added to templates in much the same way as helpers are: by calling `Template.templateName.events(...)` with a dictionary. The keys describe the event to listen for, and the values are _event handlers_ that are called when the event happens.
diff --git a/content/blaze/step09.md b/content/blaze/step09.md
index cce2f89..2968747 100644
--- a/content/blaze/step09.md
+++ b/content/blaze/step09.md
@@ -6,7 +6,7 @@ Before this step, any user of the app could edit any part of the database. This
 
 ### Removing `insecure`
 
-Every newly created Meteor project has the `insecure` package added by default. This is the package that allows us to edit the database from the client. It's useful when prototyping, but now we are taking off the training wheels. To remove this package, go to your app directory and run:
+Remember when we added `insecure` earlier? This is the package that allows us to edit the database from the client. It's useful when prototyping, but now we are taking off the training wheels. To remove this package, go to your app directory and run:
 
 ```bash
 meteor remove insecure