Merge pull request #4 from inglele/patch-1

Typo in "Choose the domains to include" section

Author: webprofusion-chrisc

docs/certificate-process.md

@@ -8,7 +8,7 @@ When you install Certify you will be prompted to register with the Let's Encrypt
 ## Requesting a Certificate
 
 ### 1. Choose the domains to include
-The first step of requesting a certificate if to decide which domain (and subdomains) need to be included in your certificate. You can manually specify these or you can load the configured hostname bindings from an existing IIS site on your server. If you choose an existing IIS site this will also be your default target for the final https bindings to be created/updated.
+The first step of requesting a certificate is to decide which domain (and subdomains) need to be included in your certificate. You can manually specify these or you can load the configured hostname bindings from an existing IIS site on your server. If you choose an existing IIS site this will also be your default target for the final https bindings to be created/updated.
 
 ### 2. Decide how to validate domains
 You will need to prove you control the domains you have added to your certificate. Only public domains can be validated using Let's Encrypt so intranet sites (hostname only with no domain etc e.g. SRVDEVAPP01) are not supported, however public domain names (like srvdevapp01.dev.domain.com) are fine.
@@ -25,4 +25,4 @@ You can customise this behaviour or even opt to have no deployment at all, howev
 There are a number of options available to customise the request/renewal process. See full guide to the user interface [options](ui-options.md) available.
 
 ### 4. Preview
-Using the *Preview* tab you can see a detailed summary of how your Managed Certificate is configured and what actions the app will plan to take next, including how the new certificate will be deployed.
+Using the *Preview* tab you can see a detailed summary of how your Managed Certificate is configured and what actions the app will plan to take next, including how the new certificate will be deployed.