removed the <kbd> component (#19305)

marciocloudflare · web-flow · commit d48f5917e5c0 · 2025-01-20T11:54:38.000Z
diff --git a/src/content/docs/1.1.1.1/setup/macos.mdx b/src/content/docs/1.1.1.1/setup/macos.mdx
@@ -14,7 +14,7 @@ import { Render } from "~/components"
 
 Take note of any DNS addresses you might have set up, and save them in a safe place in case you need to use them later.
 
-1. Go to **System Settings**. You can find it by pressing <kbd>Command</kbd> + <kbd>Space</kbd> on your keyboard and typing `System Settings`.
+1. Go to **System Settings**. You can find it by pressing `CMD + Space` on your keyboard and typing `System Settings`.
 2. Go to **Network**.
 3. Select a network service.
 4. Select **Details**.
diff --git a/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx b/src/content/docs/analytics/graphql-api/getting-started/compose-graphql-query.mdx
@@ -45,7 +45,7 @@ The text at the bottom of the list displays a short description of the data that
 the node returns.
 
 Select the dataset you want to query and insert it. Either select the item in the
-list, or scroll using arrow keys and press <kbd>Return</kbd>.
+list, or scroll using arrow keys and press the `Return` key.
 
 ## Supply required parameters
 
diff --git a/src/content/docs/cloudflare-one/connections/connect-networks/deploy-tunnels/deployment-guides/ansible.mdx b/src/content/docs/cloudflare-one/connections/connect-networks/deploy-tunnels/deployment-guides/ansible.mdx
@@ -34,7 +34,7 @@ Terraform and Ansible require an unencrypted SSH key to connect to the GCP serve
    ssh-keygen -t rsa -f ~/.ssh/gcp_ssh -C <username in GCP>
    ```
 
-2. When prompted for a passphrase, press <kbd>Enter</kbd> twice to leave it blank. Terraform cannot decode encrypted private keys.
+2. When prompted for a passphrase, press the `Enter` key twice to leave it blank. Terraform cannot decode encrypted private keys.
 
 Two files will be generated: `gcp_ssh` which contains the private key, and `gcp_ssh.pub` which contains the public key.
 
diff --git a/src/content/docs/cloudflare-one/policies/browser-isolation/accessibility.mdx b/src/content/docs/cloudflare-one/policies/browser-isolation/accessibility.mdx
@@ -12,7 +12,7 @@ Browser Isolation has a built-in screen reader which enables people with visual
 
 ### Keyboard shortcut
 
-To turn on or off the built-in screen reader, press <kbd>Ctrl</kbd> <kbd>Alt</kbd> <kbd>Z</kbd>.
+To turn on or off the built-in screen reader, press `CTRL + ALT + Z`.
 
 ### Drop-down menu
 
diff --git a/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx b/src/content/docs/cloudflare-one/policies/browser-isolation/setup/clientless-browser-isolation.mdx
@@ -93,7 +93,7 @@ Selecting **Expand** or the hostname text will expand the notch to the full addr
 
 ### Full address bar view
 
-The full address bar allows users to search and go to isolated websites. Users can jump to the address bar at any time by pressing <kbd>CTRL</kbd> + <kbd>L</kbd> on the keyboard.
+The full address bar allows users to search and go to isolated websites. Users can jump to the address bar at any time by pressing `CTRL + L` on the keyboard.
 
 ![Viewing full address of an isolated page in the clientless remote browser](~/assets/images/cloudflare-one/policies/rbi-address-bar-full.png)
 
diff --git a/src/content/docs/magic-wan/configuration/manually/third-party/fortinet.mdx b/src/content/docs/magic-wan/configuration/manually/third-party/fortinet.mdx
@@ -497,7 +497,7 @@ fortigate # 2023-08-01 09:27:26 id=20085 trace_id=2871 func=print_pkt_detail lin
 
 ### Disable Flow Debugging
 
-The typical use of <kbd>CTRL</kbd> <kbd>C</kbd> will not stop Flow Debugging.
+The typical use of `CTR + C` will not stop Flow Debugging.
 
 You can disable Flow Debugging simply by typing the following at any point while the debug logs are scrolling by:
 
diff --git a/src/content/docs/magic-wan/configuration/manually/third-party/juniper.mdx b/src/content/docs/magic-wan/configuration/manually/third-party/juniper.mdx
@@ -729,7 +729,7 @@ The log file can be viewed by doing the following:
 	tail -f /var/log/ike-debug.log
 	```
 
-3. Press  <kbd>CTRL</kbd> + <kbd>C</kbd> when finished.
+3. Press `CTRL + C` when finished.
 4. Type `exit` to return to the operational mode prompt.
 
 Either deactivate `traceoptions` or delete `traceoptions` once debugging is complete.
diff --git a/src/content/docs/warp-client/get-started/windows.mdx b/src/content/docs/warp-client/get-started/windows.mdx
@@ -42,6 +42,6 @@ The Windows application places log files in two locations based on what part of
 
 ## How to remove the application
 
-1. Select the **Start** menu and search for **Settings**. You can also press <kbd>⊞ Win</kbd> + <kbd>i</kbd>).
+1. Select the **Start** menu and search for **Settings**. You can also press `⊞ Win + I`.
 2. Select **Apps** > **App & Features**.
 3. Scroll down to Cloudflare WARP and select **Uninstall**.
diff --git a/src/content/docs/workers/observability/dev-tools/cpu-usage.mdx b/src/content/docs/workers/observability/dev-tools/cpu-usage.mdx
@@ -24,11 +24,11 @@ to specific routes, or using production-like data with the [--remote flag](/work
 To generate a CPU profile:
 
 - Run `wrangler dev` to start your Worker
-- Hit <kbd>d</kbd> from your terminal to open DevTools
-- Click on the "Profiler" tab
-- Click `Start` to begin recording CPU usage
+- Press the `D` key from your terminal to open DevTools
+- Select the "Profiler" tab
+- Select `Start` to begin recording CPU usage
 - Send requests to your Worker from a new tab
-- Click `Stop`
+- Select `Stop`
 
 You now have a CPU profile.
 
@@ -64,7 +64,7 @@ export default {
 You want to find which part of the code causes slow response times. How do you use DevTool profiling to identify the
 CPU-heavy code and fix the issue?
 
-First, as mentioned above, you open DevTools by hitting <kbd>d</kbd> after running `wrangler dev`. Then, you
+First, as mentioned above, you open DevTools by pressing the `D` key after running `wrangler dev`. Then, you
 navigate to the "Profiler" tab and take a profile by pressing `Start` and sending a request.
 
 ![CPU Profile](~/assets/images/workers/observability/profile.png)
diff --git a/src/content/docs/workers/observability/dev-tools/index.mdx b/src/content/docs/workers/observability/dev-tools/index.mdx
@@ -17,7 +17,7 @@ You may have experience using Chrome's DevTools for frontend development. Notabl
 
 ## Opening DevTools
 
-To get started, run your Worker in development mode with `wrangler dev`, then open the DevTools in the browser by hitting <kbd>d</kbd> from your terminal. Now when you access this worker locally, it can be debugged and profiled with this DevTools instance.
+To get started, run your Worker in development mode with `wrangler dev`, then open the DevTools in the browser by pressing the `D` key from your terminal. Now when you access this worker locally, it can be debugged and profiled with this DevTools instance.
 
 Alternatively, both the [Cloudflare Dashboard](https://dash.cloudflare.com/) and the [Worker's Playground](https://workers.cloudflare.com/playground) include DevTools in their UI.
 
diff --git a/src/content/docs/workers/observability/dev-tools/memory-usage.mdx b/src/content/docs/workers/observability/dev-tools/memory-usage.mdx
@@ -23,11 +23,11 @@ to specific routes, or using production-like data with the [--remote flag](/work
 To generate a memory snapshot:
 
 - Run `wrangler dev` to start your Worker
-- Hit <kbd>d</kbd> from your terminal to open DevTools
-- Click on the "Memory" tab
+- Press the `D` from your terminal to open DevTools
+- Select on the "Memory" tab
 - Send requests to your Worker to start allocating memory
   - Optionally include a debugger to make sure you can pause execution at the proper time
-- Click `Take snapshot`
+- Select `Take snapshot`
 
 You can now inspect Worker memory.
 
@@ -50,7 +50,7 @@ export default {
 While this code worked well initially, over time you notice slower responses and
 Out of Memory errors. Using DevTools, you can find out if this is a memory leak.
 
-First, as mentioned above, you open DevTools by hitting <kbd>d</kbd> after running `wrangler dev`.
+First, as mentioned above, you open DevTools by pressing the `D` key after running `wrangler dev`.
 Then, you navigate to the "Memory" tab.
 
 Next, generate a large volume of traffic to the Worker by sending requests. You can do this with `curl` or by
