fixes typos

Author: davidsmatlak

articles/governance/policy/concepts/definition-structure-parameters.md

@@ -27,7 +27,7 @@ A parameter uses the following properties in a policy definition:
   - `strongType`: (Optional) Used when assigning the policy definition through the portal. Provides a context aware list. For more information, see [strongType](#strongtype).
   - `assignPermissions`: (Optional) Set as _true_ to have Azure portal create role assignments during policy assignment. This property is useful in case you wish to assign permissions outside the assignment scope. There's one role assignment per role definition in the policy (or per role definition in all of the initiative's policies). The parameter value must be a valid resource or scope.
   - `deprecated`: A boolean flag to indicate whether a parameter is deprecated in a built-in definition.
-- `defaultValue`: (Optional) Sets the value of the parameter in an assignment if no value is given. Required when updating an existing policy definition that is assigned. For oject-type parameters, the value must match the appropriate schema.
+- `defaultValue`: (Optional) Sets the value of the parameter in an assignment if no value is given. Required when updating an existing policy definition that is assigned. For object-type parameters, the value must match the appropriate schema.
 - `allowedValues`: (Optional) Provides an array of values that the parameter accepts during assignment.
   - Case sensitivity: Allowed value comparisons are case-sensitive when assigning a policy, meaning that the selected parameter values in the assignment must match the casing of values in the `allowedValues` array in the definition. However, once values are selected for the assignment, evaluation of string comparisons might be case insensitive depending on the [condition](./definition-structure-policy-rule.md#conditions) used. For example, if the parameter specifies `Dev` as an allowed tag value in an assignment, and this value is compared to an input string using the `equals` condition, then Azure Policy would later evaluate a tag value of `dev` as a match even though it's lowercase because `notEquals` is case insensitive.
   - For object-type parameters, the values must match the appropriate schema.

articles/governance/policy/concepts/policy-as-code.md

@@ -147,7 +147,7 @@ or the initiative(s) it's part of should then be assigned to resources in the en
 from production. This environment is typically _Dev_.
 
 >[!NOTE]
-> In this step, we are conducting integration testing of the policy definition within your Azure environment, this is seperate from [verfying the functionality of the policy definition](./evaluate-impact.md#test-your-policys-effectiveness) which should occur during the definition creation process.
+> In this step, we are conducting integration testing of the policy definition within your Azure environment, this is separate from [verifying the functionality of the policy definition](./evaluate-impact.md#test-your-policys-effectiveness) which should occur during the definition creation process.
 
 The assignment should use [enforcementMode](./assignment-structure.md#enforcement-mode) of
 _disabled_ so that resource creation and updates aren't blocked, but that existing resources are

articles/governance/policy/how-to/remediate-resources.md

@@ -312,7 +312,7 @@ To create a **remediation task** with Azure PowerShell, use the `Start-AzPolicyR
 # Login first with Connect-AzAccount if not using Cloud Shell
 
 # Create a remediation for a specific assignment
-Start-AzPolicyRemediation -Name 'myRemedation' -PolicyAssignmentId '/subscriptions/{subscriptionId}/providers/Microsoft.Authorization/policyAssignments/{myAssignmentId}'
+Start-AzPolicyRemediation -Name 'myRemediation' -PolicyAssignmentId '/subscriptions/{subscriptionId}/providers/Microsoft.Authorization/policyAssignments/{myAssignmentId}'
 ```
 
 You might also choose to adjust remediation settings through these optional parameters:

articles/governance/resource-graph/concepts/guidance-for-throttled-requests.md

@@ -64,7 +64,7 @@ small and targeted queries. The group size is recommended to be less than _300_.
   {
       var userQueryRequest = new QueryRequest(
           subscriptions: new[] { subscriptionId },
-          query: "Resoures | project name, type");
+          query: "Resources | project name, type");
 
       var azureOperationResponse = await this.resourceGraphClient
           .ResourcesWithHttpMessagesAsync(userQueryRequest, header)