From 26135438e23b9971c8e1a6a01598cbdce495c3d8 Mon Sep 17 00:00:00 2001
From: "opensearch-trigger-bot[bot]"
 <98922864+opensearch-trigger-bot[bot]@users.noreply.github.com>
Date: Wed, 7 Aug 2024 14:08:40 +0000
Subject: [PATCH] Update users-roles.md (#7924) (#7927)

---
 _security/access-control/users-roles.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/_security/access-control/users-roles.md b/_security/access-control/users-roles.md
index b6157bf2d9..b182e1576a 100644
--- a/_security/access-control/users-roles.md
+++ b/_security/access-control/users-roles.md
@@ -136,7 +136,7 @@ As with any role in OpenSearch, a read-only role can be configured using the fol
 - Using the Cluster Settings API 
 
 The simplest way to get familiar with roles and role mappings is to use OpenSearch Dashboards. The interface simplifies creating roles and assigning those roles to users, with an easy-to-navigate workflow. 
-{ .tip}
+{: .tip}
 
 ### Defining a basic read-only role