to* typo

e2e_samples/parking_sensors/README.md

@@ -446,7 +446,7 @@ The following lists some limitations of the solution and associated deployment s
   - **Workaround**: Deployment add sensitive configuration as "secrets" in Variable Groups with the downside of duplicated information. If you wish, you may manually link a second Variable Group to KeyVault to pull out the secrets. KeyVault secret names should line up with required variables in the Azure DevOps pipelines. See [here](https://docs.microsoft.com/en-us/azure/devops/pipelines/library/variable-groups?view=azure-devops&tabs=yaml#link-secrets-from-an-azure-key-vault) for more information.
 - Azure DevOps Service Connection Removal: If you encounter an error like: *"Cannot delete this service connection while federated credentials for app <app-id> exist in Entra tenant <tenant-id>. Please make sure federated credentials have been removed prior to deleting the service connection."* This issue occurs when you try to delete a Service Connection in the Azure DevOps (AzDo) portal, but the Service Connection has federated credentials that need to be manually removed from the Azure Portal.
   - **Workaround - Manually Deleting Federated Credentials:**
-    Navigate o the Azure portal and find your app registration under App Registrations. In the left-hand navigation menu, choose Certificates & Secrets, then navigate to the Federated Credentials tab. Remove the federated credential from this section. After deleting the credential, proceed to delete the app registration in the Azure portal and the Azure Service Connection in the Azure DevOps (AzDo) portal.
+    Navigate to the Azure portal and find your app registration under App Registrations. In the left-hand navigation menu, choose Certificates & Secrets, then navigate to the Federated Credentials tab. Remove the federated credential from this section. After deleting the credential, proceed to delete the app registration in the Azure portal and the Azure Service Connection in the Azure DevOps (AzDo) portal.
 - Azure DevOps Environment and Approval Gates can only be managed via the UI, cannot be managed programmatically and was not incorporated in the automated deployment of the solution.
   - **Workaround**: Approval Gates can be easily configured manually. See [here](https://docs.microsoft.com/en-us/azure/devops/pipelines/process/environments?view=azure-devops#approvals) for more information.
 - ADF publishing through the CI/CD pipeline using the npm task still throws and error in the logs due to the missing publish_config.json file but the pipeline completes successfully.