Skip to content

Commit 93295c9

Browse files
committed
fix relative link
1 parent 82abfb0 commit 93295c9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/docs/how-tos/connect-via-ssh.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Nebari includes a package called [`jupyterhub-ssh`](https://github.com/yuvipanda
1212

1313
:::note
1414
There is a distinction between the Nebari and JupyterHub servers, though these are easily conflated by end users.
15-
Nebari itself is generally accessed via [kubectl](/how-tos/debug-nebari#installing-kubectl)
15+
Nebari itself is generally accessed via [kubectl](/docs/how-tos/debug-nebari#installing-kubectl)
1616
to connect directly to the cluster (nodes or pods), while the JupyterHub server runs _on_ Nebari and controls the spawning of
1717
user instances of JupyterLab. The approach described here uses a JupyterHub plugin, `jupyterhub-ssh`, to spawn and access users' JupyterLab instance
1818
:::

0 commit comments

Comments
 (0)