diff --git a/website/content/docs/configuration/session-recording/configure-worker-storage.mdx b/website/content/docs/configuration/session-recording/configure-worker-storage.mdx
index 09a5c18848..0652a8aa2e 100644
--- a/website/content/docs/configuration/session-recording/configure-worker-storage.mdx
+++ b/website/content/docs/configuration/session-recording/configure-worker-storage.mdx
@@ -68,7 +68,7 @@ Boundary uses the permission states to determine the remote storage state of a w
 
 Boundary periodically checks the states of any workers that use the external storage, and then reports them back to the controller.
 
-You can check the remote storage state of a worker using the `boundary worker read -id $WORKER_ID` command.
+You can check the remote storage state of a worker using the `boundary workers read -id $WORKER_ID` command.
 
 ```
 Worker information:
diff --git a/website/content/docs/configuration/session-recording/enable-session-recording.mdx b/website/content/docs/configuration/session-recording/enable-session-recording.mdx
index 5934d9054f..33f4ee387e 100644
--- a/website/content/docs/configuration/session-recording/enable-session-recording.mdx
+++ b/website/content/docs/configuration/session-recording/enable-session-recording.mdx
@@ -23,6 +23,7 @@ Refer to [Create the controller configuration](/boundary/docs/install-boundary/c
 - The targets must be configured with an ingress or egress worker filter that includes a worker with access to the storage bucket you created.
 Refer to [SSH target attributes](/boundary/docs/concepts/domain-model/targets#ssh-target-attributes) for more information.
 - You must enable injected application credentials on any target that you want to use for session recording.
+Refer to [Configure targets with credential injection](/boundary/docs/configuration/credential-management/configure-credential-injection) for more information about injecting application credentials.
 
 Complete the following steps to enable session recording on a target.