summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorsriramsr <sriramsr@chromium.org>2015-12-09 11:49:10 -0800
committerCommit bot <commit-bot@chromium.org>2015-12-09 19:50:08 +0000
commit55d7efa4349ccb12fe50b2999248fc69570ae040 (patch)
treea992637221908518b0d34f5b851abdaf9ebe10d1 /docs
parentcec9b85a97f28b2ff5c1cf086c89fe63ed6edc89 (diff)
downloadchromium_src-55d7efa4349ccb12fe50b2999248fc69570ae040.zip
chromium_src-55d7efa4349ccb12fe50b2999248fc69570ae040.tar.gz
chromium_src-55d7efa4349ccb12fe50b2999248fc69570ae040.tar.bz2
Fix link to Zygote process documentation.
BUG= Review URL: https://codereview.chromium.org/1506233004 Cr-Commit-Position: refs/heads/master@{#364129}
Diffstat (limited to 'docs')
-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