aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/versions/master/docs/rule-challenges.md
diff options
context:
space:
mode:
Diffstat (limited to 'site/versions/master/docs/rule-challenges.md')
-rw-r--r--site/versions/master/docs/rule-challenges.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/site/versions/master/docs/rule-challenges.md b/site/versions/master/docs/rule-challenges.md
index 7b92655b91..e69e6472b9 100644
--- a/site/versions/master/docs/rule-challenges.md
+++ b/site/versions/master/docs/rule-challenges.md
@@ -119,7 +119,7 @@ itself and its dependencies.
Above, we argued that in order to be correct, Bazel needs to know all the input
files that go into a build step in order to detect whether that build step is
still up-to-date. The same is true for package loading and rule analysis, and we
-have designed [Skyframe] (http://www.bazel.io/docs/skyframe.html) to handle this
+have designed [Skyframe] (http://www.bazel.build/docs/skyframe.html) to handle this
in general. Skyframe is a graph library and evaluation framework that takes a
goal node (such as ‘build //foo with these options’), and breaks it down into
its constituent parts, which are then evaluated and combined to yield this