Merge branch 'master' of github.com:jovrtn/github-action-wpengine-git-deploy

* 'master' of github.com:jovrtn/github-action-wpengine-git-deploy:
  Clarify SSH key setup in README
  Fix typo in README

Author: jovrtn

README.md

@@ -11,7 +11,7 @@ workflow "Deploy to WP Engine" {
 }
 
 action "Git Push to Production" {
-  uses = "jovrtn/github-action-wpengine-deploy@master"
+  uses = "jovrtn/github-action-wpengine-git-deploy@master"
   env = {
     WPENGINE_ENVIRONMENT_NAME   = "my-cool-site-production"
   }
@@ -47,5 +47,5 @@ action "Git Push to Production" {
 
 1. [Generate a new SSH key pair](https://help.github.com/articles/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent/) as a special deploy key. The simplest method is to generate a key pair with a blank passphrase, which creates an unencrypted private key.
 2. Store your public and private keys in your GitHub repository as new 'Secrets' (under your repository settings), using the names `WPENGINE_SSH_KEY_PRIVATE` and `WPENGINE_SSH_KEY_PUBLIC` respectively. In theory, this replaces the need for encryption on the key itself, since GitHub repository secrets are encrypted by default.
-3. Add the public key to your WP Engine production environment.
+3. Add the public key to your target WP Engine environment.
 4. Per the [WP Engine documentation](https://wpengine.com/git/), it takes about 30-45 minutes for the new SSH key to become active.