Merge pull request #69 from seifrajhi/patch-1

fix typos

README.md

@@ -21,10 +21,10 @@ Azure is the newest with AWS having the most supported resources
 Feel free to submit PR or Issue if you find an issue or even better add new resources, and then I'll take a look at
 merging it ASAP.
 
-**CAVEAT** The outputs of this tool are your first step, if you have AWS your can now generate resources partially, there are no conditions and even partial resources are wildcarded (for now)
+**CAVEAT** The outputs of this tool are your first step, if you have AWS, you can now generate resources partially, there are no conditions and even partial resources are wildcarded (for now).
 (for AWS)
-**best practice** would go further (and I am working on it as well), you need will to modify these permissions to the minimum required in your enviornment by adding these
-restrictions, you can also deploy using short lived credentials (usinmg this tool or Vault) (in AWS so far), generatING short-lived credentials for your build
+**best practice** would go further (and I am working on it as well), you will need to modify these permissions to the minimum required in your enviornment by adding these
+restrictions, you can also deploy using short lived credentials (using this tool or Vault) (in AWS so far), generating short-lived credentials for your build
 and then remotely (REMOTE) supply and invoke your builds (INVOKE).
 
 Ideally I would like to do this for you, but these policies are currently determined statically (QUICKER), and unrecorded intentions can be impossible to infer.