diff --git a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-routerchecker.md b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-routerchecker.md
index 91323b93a..47c275e65 100644
--- a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-routerchecker.md
+++ b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-routerchecker.md
@@ -20,7 +20,7 @@ metadata:
   name: routerchecker 
 spec:
   type: middleware.http.routerchecker
-  version: v1gi
+  version: v1
   metadata:
   - name: rule
     value: "^[A-Za-z0-9/._-]+$"
@@ -68,4 +68,4 @@ spec:
 
 - [Middleware]({{< ref middleware.md >}})
 - [Configuration concept]({{< ref configuration-concept.md >}})
-- [Configuration overview]({{< ref configuration-overview.md >}})
\ No newline at end of file
+- [Configuration overview]({{< ref configuration-overview.md >}})
diff --git a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-wasm.md b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-wasm.md
index 6ee2d58d0..7740073cb 100644
--- a/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-wasm.md
+++ b/daprdocs/content/en/reference/components-reference/supported-middleware/middleware-wasm.md
@@ -7,14 +7,21 @@ aliases:
 - /developing-applications/middleware/supported-middleware/middleware-wasm/
 ---
 
-The WASM [HTTP middleware]({{< ref middleware.md >}}) component enables you to use a WASM module to handle requests and responses.
-Using WASM modules allow developers to write middleware components in any WASM supported language and extend Dapr using external files that are not pre-compiled into the `daprd` binary.
+WebAssembly is a way to safely run code compiled in other languages. Runtimes
+execute WebAssembly Modules (Wasm), which are most often binaries with a `.wasm`
+extension.
 
-WASM modules are loaded from a filesystem path. On Kubernetes, see [mounting volumes to the Dapr sidecar]({{> kubernetes-volume-mounts.md >}}) to configure a filesystem mount that can contain WASM modules.
+The Wasm [HTTP middleware]({{< ref middleware.md >}}) allows you to rewrite a
+request URI with custom logic compiled to a Wasm binary. In other words, you
+can extend Dapr using external files that are not pre-compiled into the `daprd`
+binary. Dapr embeds [wazero][https://wazero.io] to accomplish this without CGO.
+
+Wasm modules are loaded from a filesystem path. On Kubernetes, see [mounting
+volumes to the Dapr sidecar]({{> kubernetes-volume-mounts.md >}}) to configure
+a filesystem mount that can contain Wasm modules.
 
 ## Component format
 
-
 ```yaml
 apiVersion: dapr.io/v1alpha1
 kind: Component
@@ -26,21 +33,27 @@ spec:
   metadata:
   - name: path
     value: "./hello.wasm"
-  - name: runtime
-    value: "wazero"
+  - name: poolSize
+    value: 1
 ```
 
 ## Spec metadata fields
 
-| Field | Details | Example |
-|-------|---------|---------|
-| path | A relative or absolute path to the WASM module | "./hello.wasm" |
-| runtime | The WASM runtime of your WASM binary. Only `wazero` is supported | ["wazero"](https://github.com/tetratelabs/wazero) |
+Minimally, a user must specify a Wasm binary that contains the custom logic
+used to rewrite requests. An instance of the Wasm binary is not safe to use
+concurrently. The below configuration fields control both the binary to
+instantiate and how large an instance pool to use. A larger pool allows higher
+concurrency while consuming more memory.
 
+| Field    | Details                                                        | Required | Example        |
+|----------|----------------------------------------------------------------|----------|----------------|
+| path     | A relative or absolute path to the Wasm binary to instantiate. | true     | "./hello.wasm" |
+| poolSize | Number of concurrent instances of the Wasm binary. Default: 10 | false    | 1              |
 
 ## Dapr configuration
 
-To be applied, the middleware must be referenced in [configuration]({{< ref configuration-concept.md >}}). See [middleware pipelines]({{< ref "middleware.md#customize-processing-pipeline">}}).
+To be applied, the middleware must be referenced in [configuration]({{< ref configuration-concept.md >}}).
+See [middleware pipelines]({{< ref "middleware.md#customize-processing-pipeline">}}).
 
 ```yaml
 apiVersion: dapr.io/v1alpha1
@@ -54,8 +67,45 @@ spec:
       type: middleware.http.wasm.basic
 ```
 
+### Generating Wasm
+
+This component allows you to rewrite a request URI with custom logic compiled
+to a Wasm using the waPC protocol. The `rewrite` function receives the request
+URI and returns an update as necessary.
+
+To compile your Wasm, you must compile source using a waPC guest SDK such as
+[TinyGo](https://github.com/wapc/wapc-guest-tinygo).
+
+Here's an example in TinyGo:
+
+```go
+package main
+
+import "github.com/wapc/wapc-guest-tinygo"
+
+func main() {
+	wapc.RegisterFunctions(wapc.Functions{"rewrite": rewrite})
+}
+
+// rewrite returns a new URI if necessary.
+func rewrite(requestURI []byte) ([]byte, error) {
+	if string(requestURI) == "/v1.0/hi" {
+		return []byte("/v1.0/hello"), nil
+	}
+	return requestURI, nil
+}
+```
+
+If using TinyGo, compile as shown below and set the spec metadata field named
+"path" to the location of the output (ex "example.wasm"):
+
+```bash
+tinygo build -o example.wasm -scheduler=none --no-debug -target=wasi example.go`
+```
+
 ## Related links
 
 - [Middleware]({{< ref middleware.md >}})
 - [Configuration concept]({{< ref configuration-concept.md >}})
 - [Configuration overview]({{< ref configuration-overview.md >}})
+- [waPC protocol](https://wapc.io/docs/spec/)