diff --git a/README.md b/README.md
index 6125b6e..9c45e8c 100644
--- a/README.md
+++ b/README.md
@@ -33,7 +33,7 @@ Sending a web push message to a visitor of your website requires a number of ste
 
 1. Your server has (optionally) generated (one-time) a set of [Voluntary Application server Identification (VAPID)](https://tools.ietf.org/html/draft-ietf-webpush-vapid-01) keys. Otherwise, to send messages through Chrome, you have registered your site through the [Google Developer Console](https://console.developers.google.com/) and have obtained a GCM sender id and GCM API key from your app settings.
 2. A `manifest.json` file, linked from your user's page, identifies your app settings.
-3. Also in the user's web browser, a `serviceWorker` is installed and activated and its `pushManager` property is subscribed to push events with your VAPID public key, with creates a `subscription` JSON object on the client side.
+3. Also in the user's web browser, a `serviceWorker` is installed and activated and its `pushManager` property is subscribed to push events with your VAPID public key, which creates a `subscription` JSON object on the client side.
 4. Your server uses the `webpush` gem to send a notification with the `subscription` obtained from the client and an optional payload (the message).
 5. Your service worker is set up to receive `'push'` events. To trigger a desktop notification, the user has accepted the prompt to receive notifications from your site.