diff --git a/README.md b/README.md
index 1c21947..11dcfe4 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,8 @@
-# @sanity/secrets
+# @sanity/studio-secrets
 
 > **NOTE**
 >
-> This is the **Sanity Studio v3 version** of sanity-secrets, @sanity/secrets.
+> This is the **Sanity Studio v3 version** of sanity-secrets, @sanity/studio-secrets.
 >
 > For the v2 version, please refer to the [v2-branch](https://github.com/sanity-io/sanity-secrets).
 
@@ -21,13 +21,13 @@ When native server-side secrets handling is available on the Sanity platform thi
 ## Installation
 
 ```
-npm install --save @sanity/secrets@studio-v3
+npm install --save @sanity/studio-secrets@studio-v3
 ```
 
 or
 
 ```
-yarn add @sanity/secrets@studio-v3
+yarn add @sanity/studio-secrets@studio-v3
 ```
 
 ## Usage
@@ -36,7 +36,7 @@ Quick example of both using the secrets and putting up a dialog to let user ente
 
 ```javascript
 import {useEffect, useState} from 'react'
-import {useSecrets, SettingsView} from '@sanity/secrets'
+import {useSecrets, SettingsView} from '@sanity/studio-secrets'
 
 const namespace = "myPlugin";
 
diff --git a/package-lock.json b/package-lock.json
index 9d352ba..e56fcca 100644
--- a/package-lock.json
+++ b/package-lock.json
@@ -1,11 +1,11 @@
 {
-  "name": "@sanity/secrets",
+  "name": "@sanity/studio-secrets",
   "version": "2.0.0-v3-studio.5",
   "lockfileVersion": 2,
   "requires": true,
   "packages": {
     "": {
-      "name": "@sanity/secrets",
+      "name": "@sanity/studio-secrets",
       "version": "2.0.0-v3-studio.5",
       "license": "MIT",
       "dependencies": {