aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/remote-execution-sandbox.md
diff options
context:
space:
mode:
authorGravatar spomorski <spomorski@google.com>2018-06-14 07:50:51 -0700
committerGravatar Copybara-Service <copybara-piper@google.com>2018-06-14 07:52:25 -0700
commit518568ff79512c0867822aeab0d86a1e2322bd6d (patch)
tree1f3b7ec05a14d415d95f5836bb9e6b9ca1521700 /site/docs/remote-execution-sandbox.md
parent2bcf7cd63658c29b48b41a70d1f9b8a5701f69ad (diff)
Add missing space.
PiperOrigin-RevId: 200555806
Diffstat (limited to 'site/docs/remote-execution-sandbox.md')
-rw-r--r--site/docs/remote-execution-sandbox.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/site/docs/remote-execution-sandbox.md b/site/docs/remote-execution-sandbox.md
index a7adbbf92b..e58579db73 100644
--- a/site/docs/remote-execution-sandbox.md
+++ b/site/docs/remote-execution-sandbox.md
@@ -109,7 +109,7 @@ This method executes Bazel and all of its build actions directly on the local
machine and is a reliable way to confirm whether your build will succeed when
executed remotely.
-However, with this method, locally installed tools, binaries,and data may leak
+However, with this method, locally installed tools, binaries, and data may leak
into into your build, especially if it uses [configure-style WORKSPACE rules](https://docs.bazel.build/versions/master/remote-execution-rules.html#managing-configure-style-workspace-rules).
Such leaks will cause problems with remote execution; to detect them, [troubleshoot in a Docker container](#troubleshooting-in-a-docker-container)
in addition to troubleshooting natively.