fix references to zygote_host_linux.cc
Commit a0421736a8a4: ("Move the rest of the core files in chrome\browser
to content\browser.") moved it from chrome/browser/zygote_host_linux.cc
to content/browser/zygote_host_linux.cc.
Commit c2c68b1f0c93: ("Add an API around zygoteHost so that chrome doesn't
reach into the internal content implementation.") renamed it from
content/browser/zygote_host_linux.cc to content/browser/zygote_host_impl_linux.cc.
Commit 13d6b3c13a29: ("Move zygote_host_impl_linux.* to content/browser/zygote_host")
moved it into content/browser/zygote_host.
BUG=None
Change-Id: Ie8f8fad945ec53109f67cf53462cd4af01c70d44
Reviewed-on: https://chromium-review.googlesource.com/509248
Commit-Queue: Thiago Farina <[email protected]>
Reviewed-by: Ricky Zhou <[email protected]>
Cr-Commit-Position: refs/heads/master@{#474641}diff --git a/docs/linux_zygote.md b/docs/linux_zygote.md
index da7c841..dcf57ad 100644
--- a/docs/linux_zygote.md
+++ b/docs/linux_zygote.md
@@ -36,7 +36,7 @@
The zygote process is triggered by the `--type=zygote` command line flag, which
causes `ZygoteMain` (in `chrome/browser/zygote_main_linux.cc`) to be run. The
-zygote is launched from `chrome/browser/zygote_host_linux.cc`.
+zygote is launched from `content/browser/zygote_host/zygote_host_impl_linux.cc`.
Signaling the zygote for a new renderer happens in
`chrome/browser/child_process_launcher.cc`.
