minor updates

Author: harshil1712

src/content/docs/kv/get-started.mdx

@@ -116,7 +116,7 @@ A [KV namespace](/kv/concepts/kv-namespaces/) is a key-value database replicated
 
 <Tabs syncKey = 'CLIvsDash'> <TabItem label='CLI'>
 
-[Wrangler](/workers/wrangler/) allows you to put, list, get, and delete entries within your KV namespace.
+You can use [Wrangler](/workers/wrangler/) to create a new KV namespace. You can also use it to perform operations such as put, list, get, and delete within your KV namespace.
 
 :::note
 
@@ -171,6 +171,14 @@ To create a KV namespace via Wrangler:
 
 You must create a binding to connect your Worker with your KV namespace. [Bindings](/workers/runtime-apis/bindings/) allow your Workers to access resources, like KV, on the Cloudflare developer platform.
 
+:::note[Bindings]
+
+A binding is how your Worker interacts with external resources such as [KV namespaces](/kv/concepts/kv-namespaces/). A binding is a runtime variable that the Workers runtime provides to your code. You can declare a variable name in your Wrangler file that binds to these resources at runtime, and interact with them through this variable. Every binding's variable name and behavior is determined by you when deploying the Worker.
+
+Refer to [Environment](/kv/reference/environments/) for more information.
+
+:::
+
 To bind your KV namespace to your Worker:
 
 <Tabs syncKey='CLIvsDash'><TabItem label='CLI'>
@@ -194,14 +202,6 @@ To bind your KV namespace to your Worker:
 	- Your binding is available in your Worker at `env.<BINDING_NAME>` from within your Worker. For this tutorial, the binding is available at `env.USERS_NOTIFICATION_CONFIG`.
 </Steps>
 
-:::note[Bindings]
-
-A binding is how your Worker interacts with external resources such as [KV namespaces](/kv/concepts/kv-namespaces/). A binding is a runtime variable that the Workers runtime provides to your code. You can declare a variable name in your Wrangler file that binds to these resources at runtime, and interact with them through this variable. Every binding's variable name and behavior is determined by you when deploying the Worker.
-
-Refer to [Environment](/kv/reference/environments/) for more information.
-
-:::
-
 </TabItem><TabItem label='Dashboard'>
 
 <Steps>
@@ -232,6 +232,8 @@ To write a value to your empty KV namespace using Wrangler:
 	npx wrangler kv key put --binding=<BINDING_NAME> "<KEY>" "<VALUE>"
 	```
 
+	In this tutorial, you will add a key `user_1` with value `enabled` to the KV namespace you created in [step 2](/kv/get-started/#2-create-a-kv-namespace).
+
 	```sh
 	npx wrangler kv key put --binding=USERS_NOTIFICATION_CONFIG "user_1" "enabled"
 	```
@@ -240,7 +242,7 @@ To write a value to your empty KV namespace using Wrangler:
 	```
 </Steps>
 
-:::note
+:::note[Using `--namespace-id`]
 Instead of using `--binding`, you can also use `--namespace-id` to specify which KV namespace should receive the operation:
 
 ```sh "--namespace-id=<BINDING_ID>"
@@ -252,12 +254,16 @@ Writing the value "<VALUE>" to key "<KEY>" on namespace <BINDING_ID>.
 ```
 :::
 
-To create a key and a value in local mode, add the `--local` flag at the end of the command:
+:::note[Storing values in remote KV namespace]
 
-```sh ins="--local"
-npx wrangler kv key put --namespace-id=xxxxxxxxxxxxxxxx "<KEY>" "<VALUE>" --local
+By default, the values are written locally. To create a key and a value in your remote KV namespace, add the `--remote` flag at the end of the command:
+
+```sh ins="--remote"
+npx wrangler kv key put --namespace-id=xxxxxxxxxxxxxxxx "<KEY>" "<VALUE>" --remote
 ```
 
+:::
+
 </TabItem><TabItem label = 'Dashboard'>
 <Steps>
 1. Go to [**Storage & Databases** > **KV**](https://dash.cloudflare.com/?to=/:account/workers/kv/namespaces).
@@ -274,38 +280,26 @@ npx wrangler kv key put --namespace-id=xxxxxxxxxxxxxxxx "<KEY>" "<VALUE>" --loca
 
 <Tabs syncKey='CLIvsDash'><TabItem label = 'CLI'>
 
-To access the value using Wrangler:
+To access the value from your KV namespace using Wrangler:
 
 <Steps>
 1. Run the `wrangler kv key get` subcommand in your terminal, and input your key value:
 
     ```sh
-    # Replace [OPTIONS] with --binding or --namespace-id
-    npx wrangler kv key get [OPTIONS] "<KEY>"
+    npx wrangler kv key get --binding=<BINDING_NAME> "<KEY>"
     ```
 
-    A KV namespace can be specified in two ways. Replace `[OPTIONS]` with `--binding` or `--namespace-id`:
-
-    <Details header="With a `--binding`">
-
-	```sh
-	npx wrangler kv key get --binding=<BINDING_NAME> "<KEY>"
-	```
-
-    </Details>
-
-    <Details header ="With a `--namespace-id`">
+		In this tutorial, you will get the value of the key `user_1` from the KV namespace you created in [step 2](/kv/get-started/#2-create-a-kv-namespace).
 
     ```sh
-    npx wrangler kv key get --namespace-id=<YOUR_ID> "<KEY>"
+    npx wrangler kv key get --binding=USERS_NOTIFICATION_CONFIG "user_1" --text
     ```
-    </Details>
 
-		For example, using the `--binding` option:
+	:::note
+	To view the value directly within the terminal, you use the `--text` flag.
+	:::
 
-		```sh
-		npx wrangler kv key get --binding=USERS_NOTIFICATION_CONFIG "user_1"
-		```
+    Similar to the `put` command, the `get` command can also be used to access a KV namespace in two ways - with `--binding` or `--namespace-id`:
 
 </Steps>
 
@@ -316,9 +310,7 @@ To access the value using Wrangler:
 Exactly **one** of `--binding` or `--namespace-id` is required.
 :::
 
-:::note
-To view the value directly within the terminal, add `--text`
-:::
+
 
 Refer to the [`kv bulk` documentation](/kv/reference/kv-commands/#kv-bulk) to write a file of multiple key-value pairs to a given KV namespace.
 
@@ -345,7 +337,7 @@ To have `wrangler dev` connect to your Workers KV namespace running on Cloudflar
 :::
 
 <Steps>
-1. In your Worker script, add your KV binding in the `Env` interface:
+1. In your Worker script, add your KV binding in the `Env` interface. If you have bootstrapped your project with JavaScript, this step is not required.
 
 	```ts
 	interface Env {
@@ -354,16 +346,16 @@ To have `wrangler dev` connect to your Workers KV namespace running on Cloudflar
 	}
 	```
 
-2. Use the `put()` method on `USERS_NOTIFICATION_CONFIG` to create a new key-value pair:
+2. Use the `put()` method on `USERS_NOTIFICATION_CONFIG` to create a new key-value pair. You will add a new key `user_2` with value `disabled` to your KV namespace.
 
 	```ts
-	let value = await env.USERS_NOTIFICATION_CONFIG.put(key, value);
+	let value = await env.USERS_NOTIFICATION_CONFIG.put("user_2", "disabled");
 	```
 
-3. Use the KV `get()` method to fetch the data you stored in your KV database:
+3. Use the KV `get()` method to fetch the data you stored in your KV namespace. You will fetch the value of the key `user_2` from your KV namespace.
 
 	```ts
-	let value = await env.USERS_NOTIFICATION_CONFIG.get("KEY");
+	let value = await env.USERS_NOTIFICATION_CONFIG.get("user_2");
 	```
 </Steps>
 
@@ -380,9 +372,11 @@ Your Worker code should look like this:
 
 The code above:
 
-1. Writes a key to `USERS_NOTIFICATION_CONFIG` binding using KV's `put()` method.
-2. Reads the same key using KV's `get()` method, and returns an error if the key is null (or in case the key is not set, or does not exist).
-3. Uses JavaScript's [`try...catch`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/try...catch) exception handling to catch potential errors. When writing or reading from any service, such as Workers KV or external APIs using `fetch()`, you should expect to handle exceptions explicitly.
+1. Writes a key to your KV namespace using KV's `put()` method.
+2. Reads the same key using KV's `get()` method.
+3. It checks if the key is null, and returns a `404` response if it is.
+4. If the key is not null, it returns the value of the key.
+5. Uses JavaScript's [`try...catch`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/try...catch) exception handling to catch potential errors. When writing or reading from any service, such as Workers KV or external APIs using `fetch()`, you should expect to handle exceptions explicitly.
 
 </TabItem><TabItem label = 'Dashboard'>
 
@@ -414,32 +408,7 @@ The code above:
 
 </TabItem></Tabs>
 
-## 6. Deploy your KV
-
-You can deploy your project in one of two ways:
-
-- **Locally:** Runs from your machine on a local server. The URL to your web application is only accessible while you are running the application from your terminal.
-- **Remotely:** Runs on Cloudflare's global network. The URL to your web application will be accessible to anyone with the URL.
-
-:::note
-You can only deploy your project locally through the Wrangler CLI. You can only deploy remotely when deploying through the Cloudflare dashboard.
-:::
-
-In this tutorial, we expect the URL to simply return the value `disabled` (which corresponds to the key `user_2`).
-
-### Deploy your project locally
-
-<Steps>
-1. Run the following command within your project directory:
-
-	```sh
-	npm run dev
-	```
-
-2. Visit the URL for your newly created Workers KV application running on your local machine, as provided by Wrangler (usually `localhost:8787`).
-</Steps>
-
-### Deploy your project globally
+## 6. Deploy your Worker
 
 <Tabs syncKey = 'CLIvsDash'><TabItem label = 'CLI'>