Text review and fill in Secrets Store admin description

Author: RebeccaTamachiro

src/content/docs/secrets-store/access-control.mdx

@@ -9,8 +9,8 @@ description: Learn about role-based access control with Cloudflare Secrets Store
 
 Secrets Store allows security administrators to have more control, by implementing role-based access. Refer to the list below for default role definitions. For details about roles at Cloudflare, refer to [Fundamentals](/fundamentals/setup/manage-members/).
 
-- (TBC)**Secrets Store admin**:
-- **Super administrator**: Can create, edit, delete, and view secrets. Can also add the binding to access a Secrets Store secret to a `wrangler.toml` file.
+- **Super administrator**: Can create, edit, duplicate, delete, and view secrets metadata. Can also add a [Secrets Store binding to a Worker](/secrets-store/integrations/workers/).
+- (TBC)**Secrets Store admin**: Can create, edit, duplicate, delete, and view secrets metadata. Can also add a [Secrets Store binding to a Worker](/secrets-store/integrations/workers/).
 
 ## Assign permissions
 

src/content/docs/secrets-store/manage-secrets/how-to.mdx

@@ -19,7 +19,7 @@ You must have a (TBC)[Super Administrator or Secrets Store admin role](/secrets-
 
 ## Duplicate a secret
 
-Duplicate a secret to keep the same secret value but change name, scope (once available), or comments.
+Duplicate a secret to keep the same secret value but change name, scope, or comments.
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account.
 2. Go to **Secrets Store**.
@@ -30,7 +30,11 @@ Duplicate a secret to keep the same secret value but change name, scope (once av
 
 ## Edit a secret
 
-Edit a secret to replace an existing value with a new one. This action will cause the replacement in all services using the secret.
+Edit a secret to replace an existing value with a new one.
+
+:::caution
+This action will cause the replacement in all services using the secret.
+:::
 
 You can also edit the secret **Permission scope** and **Comment**.
 

src/content/docs/secrets-store/manage-secrets/index.mdx

@@ -12,7 +12,7 @@ import { DirectoryListing, FeatureTable } from "~/components";
 
 Secrets can be API tokens, public/private keys, authorization keys, passwords, or even code variables. The only limitation is that it must be a string within 1024 bytes.
 
-Once a secret is added to the secrets store, it can no longer be decrypted or accessed via API or on the Dashboard, only the service associated with it will be able to access it.
+Once a secret is added to the secrets store, it can no longer be decrypted or accessed via API or on the Dashboard, only the service associated with a given secret will be able to access it.
 
 ## Limits