From 16f74a4eb3785a5cb2d9309fa0e22ab71b83c0b1 Mon Sep 17 00:00:00 2001
From: Reshma Abdul Rahim <61033581+Reshrahim@users.noreply.github.com>
Date: Tue, 3 Oct 2023 12:37:55 -0400
Subject: [PATCH] Fix typo in Update limitations.md

---
 docs/reference/limitations.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/reference/limitations.md b/docs/reference/limitations.md
index ddd9c18d..34f14075 100644
--- a/docs/reference/limitations.md
+++ b/docs/reference/limitations.md
@@ -3,6 +3,6 @@
 ### Non-idempotency
 If you see a warning describing an AWS resource as 'non-idempotent', this means that this resource type is assigned a primary identifier at deployment time and is currently not supported by Radius Bicep.
 
-We are currently building support for non-idempotent resources in Radius. Please like and comment on this [this issue](https://github.com/radius-project/radius/issues/6227) if you are interested in the same.
+We are currently building support for non-idempotent resources in Radius. Please like and comment on [this issue](https://github.com/radius-project/radius/issues/6227) if you are interested in the same.
 
 As a workaround, you can try using [terraform recipes](https://docs.radapp.dev/guides/recipes/overview/) to deploy and manage those non-idempotent resource types.