Use shared components

Author: penalosa

src/content/docs/workers/wrangler/resource-provisioning.mdx

@@ -7,13 +7,16 @@ sidebar:
     text: Beta
 ---
 
-# Resource Provisioning
+import { PackageManagers, WranglerConfig } from "~/components";
+
 You can now automatically provision Cloudflare resources as part of your deployment.  Without this, you need to separately manually create any resouces that do not yet exist on your account prior to deploying. 
 
-With resource provisioning, if your Wrangler configuration file includes a [KV namespace](/kv/), [D1 database](/d1/), or [R2 bucket](/r2/) that does not yet exist, Wrangler will create these resources upon deployment. This is done by adding the experimental `–x-provision` flag to your commands. 
+With resource provisioning, if your Wrangler configuration file includes a [KV namespace](/kv/), [D1 database](/d1/), or [R2 bucket](/r2/) that does not yet exist, Wrangler will create these resources upon deployment. This is done by adding the experimental `-–x-provision` flag to your commands. 
 
 ## Wrangler Configuration 
-You can set up your Wrangler configuration file like the following: 
+You can set up your Wrangler configuration file like the following:
+
+<WranglerConfig>
 ```json
 {
   "kv_namespaces": [
@@ -33,20 +36,26 @@ You can set up your Wrangler configuration file like the following:
   ]
 }
 ```
-When using the experimental `–x-provision` flag, the `id` field for KV and D1 and the `bucket_name` for R2 are optional in your wrangler configuration. 
+</WranglerConfig>
+
+When using the experimental `-–x-provision` flag, the `id` field for KV and D1 and the `bucket_name` for R2 are optional in your wrangler configuration. 
 
 ## Developing locally and deploying
 When developing locally, you can interact with local versions of any KV, D1, R2 resources configured in your Wrangler configuration file by running:
 
-```sh
-npx wrangler dev –x-provision
-```
+<PackageManagers
+	type="exec"
+	pkg="wrangler"
+	args={"dev –-x-provision"}
+/>
 
 When you're ready to deploy, run: 
 
-```sh
-npx wrangler deploy –x-provision
-```
+<PackageManagers
+	type="exec"
+	pkg="wrangler"
+	args={"deploy –-x-provision"}
+/>
 
 Upon deploy Wrangler will automatically create the resources that do not yet exist on your accound and bind them to your Worker. The newly created resource will be named with the format `<worker-name>-<binding-name>` by default.