aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/skylark/rules.md
diff options
context:
space:
mode:
Diffstat (limited to 'site/docs/skylark/rules.md')
-rw-r--r--site/docs/skylark/rules.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/site/docs/skylark/rules.md b/site/docs/skylark/rules.md
index 0f8772bf86..ed25ec9136 100644
--- a/site/docs/skylark/rules.md
+++ b/site/docs/skylark/rules.md
@@ -235,7 +235,7 @@ output*. There are multiple ways for a rule to introduce a predeclared output:
See [Executable rules](#executable-rules-and-test-rules) below.
All predeclared outputs can be accessed within the rule's implementation
-function under the [`ctx.outputs`](lib/ctx.html#output) struct; see that page
+function under the [`ctx.outputs`](lib/ctx.html#outputs) struct; see that page
for details and restrictions. Non-predeclared outputs are created during
analysis using the [`ctx.actions.declare_file`](lib/actions.html#declare_file)
and [`ctx.actions.declare_directory`](lib/actions.html#declare_directory)
@@ -666,7 +666,7 @@ specify one using `DefaultInfo`; it must not be used otherwise. This output
mechanism is deprecated because it does not support customizing the executable
file's name at analysis time.
-See examples of an [executable rule](https://github.com/bazelbuild/examples/blob/master/rules/executable/executable.bzl)
+See examples of an [executable rule](https://github.com/bazelbuild/examples/blob/master/rules/executable/fortune.bzl)
and a [test rule](https://github.com/bazelbuild/examples/blob/master/rules/test_rule/line_length.bzl).
Test rules inherit the following attributes: `args`, `flaky`, `local`,