Fixed typos

README.md

@@ -68,7 +68,7 @@ jobs:
         creds: ${{ secrets.AZURE_CREDENTIALS }}
         resourceGroupName: <YourResourceGroup>
         templateLocation: <path/to/azuredeploy.json>
-        parametersLocation: <path/to/parameters.json> OR  <KEY=VALUE>
+        parameters: <path/to/parameters.json> OR <KEY=VALUE>
         deploymentName: <Deployment base name>
 ```
 For more advanced workflows see [examples/Advanced.md](examples/Advanced.md).

examples/Advanced.md

@@ -1,6 +1,6 @@
 # Advanced example on how to use this Action
-In this exmaple we deploy 2 templates (for the sake of the example the same template) but the seccond one depends on the first one as we need first the output of first one and seccond we need to override a parameter in the seccond template.   
-Our template has two outputs `location` and `containerName`. But here we only interested in `containerName`, the first template will output that one and the seccond one requires that and appends `-overriden` so we can see it got overriden.
+In this exmaple we deploy 2 templates (for the sake of the example the same template) but the second one depends on the first one as we need first the output of first one and second we need to override a parameter in the second template.   
+Our template has two outputs `location` and `containerName`. But we are only interested in `containerName`, the first template will output that one and the second one requires that and appends `-overriden` so we can see it got overriden.
 
 ## Steps
 ```yaml
@@ -34,7 +34,7 @@ If we now add a Shell script with a simple echo from that value,
 ```
 we can see that on the console will be `github-action` printed.
 
-Now we add our seccond deployment which relies on that value and modfies the `containerName` parameter,
+Now we add our second deployment which relies on that value and modfies the `containerName` parameter,
 ```yaml
 - uses: whiteducksoftware/azure-arm-action@v3
   id: deploy2