diff --git a/modules/deploy/partials/kubernetes/guides/next-steps.adoc b/modules/deploy/partials/kubernetes/guides/next-steps.adoc
index c5c5402be..d50c42fae 100644
--- a/modules/deploy/partials/kubernetes/guides/next-steps.adoc
+++ b/modules/deploy/partials/kubernetes/guides/next-steps.adoc
@@ -1,6 +1,6 @@
 = Next steps
 
-* xref:develop:code-examples.adoc[Build a sample application]
+* xref:redpanda-labs:ROOT:index.adoc[Try an example in Redpanda Labs]
 * xref:manage:console/index.adoc[Learn more about Redpanda Console]
 * xref:get-started:rpk-install.adoc[Learn more about rpk]
 
diff --git a/modules/develop/pages/http-proxy.adoc b/modules/develop/pages/http-proxy.adoc
index 7893155cf..1be4938af 100644
--- a/modules/develop/pages/http-proxy.adoc
+++ b/modules/develop/pages/http-proxy.adoc
@@ -102,7 +102,7 @@ Curl is likely already installed on your system. If not, see https://curl.se/dow
 NodeJS::
 +
 --
-NOTE: This is based on the assumption that you're in the root directory of an existing NodeJS project. See xref:develop:guide-nodejs.adoc[Use NodeJS with Redpanda] for one way to get started with a new NodeJS project and examples of connecting to Redpanda with a native library.
+NOTE: This is based on the assumption that you're in the root directory of an existing NodeJS project. See xref:redpanda-labs:clients:docker-nodejs.adoc[] for an example of a NodeJS project.
 
 In a terminal window, run:
 
diff --git a/modules/get-started/pages/quick-start.adoc b/modules/get-started/pages/quick-start.adoc
index 9c025e4ae..fde645524 100644
--- a/modules/get-started/pages/quick-start.adoc
+++ b/modules/get-started/pages/quick-start.adoc
@@ -284,11 +284,10 @@ docker compose down -v
 
 == Next steps
 
-- xref:develop:code-examples.adoc[Continue learning about client application]
+- xref:redpanda-labs:ROOT:index.adoc[Try more examples in Redpanda Labs]
 - xref:manage:console/index.adoc[Learn more about Redpanda Console]
 - xref:rpk-install.adoc[Learn more about rpk]
 - xref:deploy:deployment-option/self-hosted/manual/production/index.adoc[Deploy for development or production]
-- xref:reference:docker-compose.adoc[Try more Docker Compose examples]
 - Find the https://hub.docker.com/r/redpandadata/redpanda[Docker images for Redpanda^] on Docker Hub
 - Find the https://hub.docker.com/r/redpandadata/console/tags[Docker images for Redpanda Console^] on Docker Hub
 
diff --git a/modules/manage/pages/security/console/plain.adoc b/modules/manage/pages/security/console/plain.adoc
index c64cedc84..f3c0ebf38 100644
--- a/modules/manage/pages/security/console/plain.adoc
+++ b/modules/manage/pages/security/console/plain.adoc
@@ -12,7 +12,7 @@ Configuring Redpanda Console with a plain login provider allows your users to au
 username and password. Plain logins are the easiest way to set up a login-protected deployment of Redpanda Console. However,
 plain logins are not secure, and Redpanda recommends them only for development environments or demo purposes.
 
-TIP: You can test this feature using Docker Compose. See the xref:reference:docker-compose.adoc#plain-login-authentication-for-redpanda-console[Plain login authentication for Redpanda Console] sample.
+TIP: You can test this feature using Docker Compose. See the xref:redpanda-labs:docker-compose:console-plain-login.adoc[Plain login authentication for Redpanda Console] sample.
 
 To configure a plain login provider, you must: