From a4c05791102bdfef87928ac2366992fd4c7dde4d Mon Sep 17 00:00:00 2001
From: Shannon Hicks <93622349+shanhix1@users.noreply.github.com>
Date: Wed, 1 May 2024 15:01:58 -0700
Subject: [PATCH] Fixed typo "inintended" to "unintended" (#1315)

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 41988853b..09bb5756e 100644
--- a/README.md
+++ b/README.md
@@ -233,7 +233,7 @@ The following resource types bypass policy evaluation:
 
 There are also scenarios in which policy evaluation is skipped for resources in managed resource groups:
 - Cross-tenant requests in RGs managed by `Microsoft.Databricks/workspaces`
-  - Policy evaluation is skipped for these scenarios, which occur at creation time when the Databricks RP deploys locked resources needed to power the service within the managed RG. This is done so that customer policy assignments do not lead to partial deployment of these resources, which could cause inintended billing and inability to modify. 
+  - Policy evaluation is skipped for these scenarios, which occur at creation time when the Databricks RP deploys locked resources needed to power the service within the managed RG. This is done so that customer policy assignments do not lead to partial deployment of these resources, which could cause unintended billing and inability to modify. 
   - Databricks resources will have policy enforcement post-creation, when requests are made within the same tenant.
   - To provide feedback on this deployment experience, please leverage the [Databricks UserVoice](https://feedback.azure.com/forums/909463-azure-databricks). 
 - Cross-tenant requests in RGs managed by `Microsoft.Solutions/applications`