summaryrefslogtreecommitdiffstats
path: root/docs/linux_suid_sandbox.md
diff options
context:
space:
mode:
Diffstat (limited to 'docs/linux_suid_sandbox.md')
-rw-r--r--docs/linux_suid_sandbox.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/linux_suid_sandbox.md b/docs/linux_suid_sandbox.md
index 5845662..6b144e9 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