diff --git a/apps/docs/content/bun/how-to/access.mdx b/apps/docs/content/bun/how-to/access.mdx
index 0a80def1..52b36040 100644
--- a/apps/docs/content/bun/how-to/access.mdx
+++ b/apps/docs/content/bun/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your Bun service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Bun service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your Bun service is not publicly accessible. When your application i
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](bun/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](bun/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/deno/how-to/access.mdx b/apps/docs/content/deno/how-to/access.mdx
index 0fde99bc..b25d9b10 100644
--- a/apps/docs/content/deno/how-to/access.mdx
+++ b/apps/docs/content/deno/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your Deno service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Deno service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your Deno service is not publicly accessible. When your application
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/deno/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/deno/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/dotnet/how-to/access.mdx b/apps/docs/content/dotnet/how-to/access.mdx
index 90dd2194..90ddd691 100644
--- a/apps/docs/content/dotnet/how-to/access.mdx
+++ b/apps/docs/content/dotnet/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your .NET service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your .NET service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your .NET service is not publicly accessible. When your application
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/dotnet/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/dotnet/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/elixir/how-to/access.mdx b/apps/docs/content/elixir/how-to/access.mdx
index 4f6ae5fa..58b02119 100644
--- a/apps/docs/content/elixir/how-to/access.mdx
+++ b/apps/docs/content/elixir/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your Elixir service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Elixir service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your Elixir service is not publicly accessible. When your applicatio
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/elixir/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/elixir/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/gleam/how-to/access.mdx b/apps/docs/content/gleam/how-to/access.mdx
index b07656c6..3a6a451a 100644
--- a/apps/docs/content/gleam/how-to/access.mdx
+++ b/apps/docs/content/gleam/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your Gleam service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Gleam service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your Gleam service is not publicly accessible. When your application
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/gleam/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/gleam/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/go/how-to/access.mdx b/apps/docs/content/go/how-to/access.mdx
index 63d3d2e7..c6ed5149 100644
--- a/apps/docs/content/go/how-to/access.mdx
+++ b/apps/docs/content/go/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your Go service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Go service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your Go service is not publicly accessible. When your application is
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/go/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/go/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/java/how-to/access.mdx b/apps/docs/content/java/how-to/access.mdx
index 09e5ea13..170d2101 100644
--- a/apps/docs/content/java/how-to/access.mdx
+++ b/apps/docs/content/java/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your Java service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Java service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your Java service is not publicly accessible. When your application
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/java/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/java/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/meilisearch/overview.mdx b/apps/docs/content/meilisearch/overview.mdx
index 6bad842b..976d483b 100644
--- a/apps/docs/content/meilisearch/overview.mdx
+++ b/apps/docs/content/meilisearch/overview.mdx
@@ -73,7 +73,7 @@ The service provides three pre-configured API keys, each with specific access le
### Access Methods
#### Public HTTPS Access
-When enabled, access via [Zerops subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+When enabled, access via [Zerops subdomain](/features/access#public-access-through-zerops-subdomain).
#### Internal Project Access
Services within the same project can reach Meilisearch directly:
diff --git a/apps/docs/content/nginx/how-to/access.mdx b/apps/docs/content/nginx/how-to/access.mdx
index f8a1c0a5..fe84265b 100644
--- a/apps/docs/content/nginx/how-to/access.mdx
+++ b/apps/docs/content/nginx/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your Nginx static service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Nginx static service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your Nginx static service is not publicly accessible. When your appl
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/nginx/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/nginx/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/nodejs/how-to/access.mdx b/apps/docs/content/nodejs/how-to/access.mdx
index 2cfda64c..6af3ee88 100644
--- a/apps/docs/content/nodejs/how-to/access.mdx
+++ b/apps/docs/content/nodejs/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your Node.js service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Node.js service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your Node.js service is not publicly accessible. When your applicati
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/nodejs/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/nodejs/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/php/how-to/access.mdx b/apps/docs/content/php/how-to/access.mdx
index 65a8d99f..5414a5a2 100644
--- a/apps/docs/content/php/how-to/access.mdx
+++ b/apps/docs/content/php/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your PHP service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your PHP service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your PHP service is not publicly accessible. When your application i
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/php/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/php/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/python/how-to/access.mdx b/apps/docs/content/python/how-to/access.mdx
index 1f9f0028..e9c172ce 100644
--- a/apps/docs/content/python/how-to/access.mdx
+++ b/apps/docs/content/python/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your Python service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Python service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your Python service is not publicly accessible. When your applicatio
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/python/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/python/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
diff --git a/apps/docs/content/rust/how-to/access.mdx b/apps/docs/content/rust/how-to/access.mdx
index 61b20b78..7f8ce98f 100644
--- a/apps/docs/content/rust/how-to/access.mdx
+++ b/apps/docs/content/rust/how-to/access.mdx
@@ -55,7 +55,7 @@ Use the `ssh` command to connect to your service v
## Public access through zerops.io subdomain
-By default, your Rust service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain).
+By default, your Rust service is not publicly accessible. To test your application, enable the [public access through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain).
## Public access through your domain
@@ -63,4 +63,4 @@ By default, your Rust service is not publicly accessible. When your application
## Public access from another Zerops project
-All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/rust/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zeropsapp-subdomain) or [through your domain](/features/access#public-access-through-your-domain).
+All services of the same project share a dedicated private network. To connect to a service within the same project, just use the service hostname and its [internal port](/rust/how-to/build-pipeline#ports). Different projects are not connected inside Zerops. To connect to a runtime service from another Zerops project, you need to use public access either [through zerops.io subdomain](/features/access#public-access-through-zerops-subdomain) or [through your domain](/features/access#public-access-through-your-domain).