Docs: Rewrite Bazel pages to clarify intended user, Part 4
PiperOrigin-RevId: 361612150
diff --git a/site/docs/remote-execution-caching-debug.md b/site/docs/remote-execution-caching-debug.md
index 583fa04..567581f 100644
--- a/site/docs/remote-execution-caching-debug.md
+++ b/site/docs/remote-execution-caching-debug.md
@@ -37,7 +37,7 @@
### Ensure re-running the same build/test command produces cache hits
1. Run the build(s) and/or test(s) that you expect to populate the cache. The
- first time a new build is run on a particular stack, we expect no remote
+ first time a new build is run on a particular stack, you can expect no remote
cache hits. As part of remote execution, action results are stored in the
cache and a subsequent run should pick them up.
