From ded23b4b3a0c3f16160d881c5be424b845fb7180 Mon Sep 17 00:00:00 2001
From: dhr-verma <137836091+dhr-verma@users.noreply.github.com>
Date: Thu, 26 Dec 2024 11:27:25 -0500
Subject: [PATCH] Update server/routerlicious/.changeset/weak-radios-camp.md

Co-authored-by: Alex Villarreal <716334+alexvy86@users.noreply.github.com>
---
 server/routerlicious/.changeset/weak-radios-camp.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/server/routerlicious/.changeset/weak-radios-camp.md b/server/routerlicious/.changeset/weak-radios-camp.md
index 5bb7ededccae..9ecee799f2ea 100644
--- a/server/routerlicious/.changeset/weak-radios-camp.md
+++ b/server/routerlicious/.changeset/weak-radios-camp.md
@@ -4,4 +4,4 @@
 
 Now Riddler supports using private keys to sign server access tokens
 
-Riddler's tenant manager now exposed two new properties - `enablePrivateKeyAccess` and `enableSharedKeyAccess`. These respectively indicate whether a tenant can be accessed using hidden private keys and whether a tenant can be accessed using shared secrets. The APIs added support toggling the `enablePrivateKeyAccess` prop. They also support fetching these new keys and refreshing these new keys. All calls to manipulate private keys should be made from witin the server.
+Riddler's tenant manager now exposes two new properties - `enablePrivateKeyAccess` and `enableSharedKeyAccess`. These respectively indicate whether a tenant can be accessed using hidden private keys and whether a tenant can be accessed using shared secrets. APIs now support toggling the `enablePrivateKeyAccess` prop. They also support fetching these new keys and refreshing these new keys. All calls to manipulate private keys should be made from within the server.