Index: docs/linux_suid_sandbox.md |
diff --git a/docs/linux_suid_sandbox.md b/docs/linux_suid_sandbox.md |
index 58456628b5f74b84c03f3b1b84797af556d5c3b7..6b144e9aa7928bbda7b561fa4d7578d520c4ab4f 100644 |
--- a/docs/linux_suid_sandbox.md |
+++ b/docs/linux_suid_sandbox.md |
@@ -9,7 +9,7 @@ renderers using a `SUID` helper binary. This is one of |
The `SUID` helper binary is called `chrome_sandbox` and you must build it |
separately from the main 'chrome' target. To use this sandbox, you have to |
specify its path in the `linux_sandbox_path` GYP variable. When spawning the |
-[zygote process](linux_zygote/md), if the `SUID` sandbox is enabled, Chromium |
+[zygote process](linux_zygote.md), if the `SUID` sandbox is enabled, Chromium |
will check for the sandbox binary at the location specified by |
`linux_sandbox_path`. For Google Chrome, this is set to |
`/opt/google/chrome/chrome-sandbox`, and early version had this value hard coded |