fix components

Author: ranbel

src/content/docs/cloudflare-one/connections/connect-devices/user-side-certificates/automated-deployment.mdx

@@ -7,7 +7,7 @@ head: []
 description: Automatically deploy a root certificate on desktop devices.
 ---
 
-import { Details, Render, APIRequest } from "~/components";
+import { Details, Render } from "~/components";
 
 <Details header="Feature availability">
 

src/content/docs/cloudflare-one/connections/connect-devices/user-side-certificates/custom-certificate.mdx

@@ -8,7 +8,7 @@ description: Configure WARP to use a custom root certificate instead of the
   Cloudflare certificate.
 ---
 
-import { Render, Tabs, TabItem, APIRequest } from "~/components";
+import { Render, Tabs, TabItem } from "~/components";
 
 :::note
 Only available on Enterprise plans.

src/content/docs/cloudflare-one/identity/devices/warp-client-checks/client-certificate.mdx

@@ -5,7 +5,7 @@ sidebar:
   order: 3
 ---
 
-import { Details, Render, TabItem, Tabs, APIRequest } from "~/components";
+import { Details, Render, TabItem, Tabs } from "~/components";
 
 The Client Certificate device posture attribute checks if the device has a valid client certificate signed by a trusted certificate. The trusted certificate is uploaded to Cloudflare and specified as part of the posture check rule. The client certificate posture check can be used in Gateway and Access policies to ensure that the user is connecting from a managed device.
 

src/content/partials/cloudflare-one/upload-mtls-cert.mdx

@@ -4,7 +4,7 @@ params:
   - key?
 ---
 
-import { Markdown, APIrequest } from "~/components";
+import { Markdown, APIRequest } from "~/components";
 
 Use the [Upload mTLS certificate endpoint](/api/resources/mtls_certificates/methods/create/) to upload the certificate and private key to Cloudflare. The certificate must be a {props.cert}, formatted as a single string with `\n` replacing the line breaks. {props.key}