aboutsummaryrefslogtreecommitdiffhomepage
path: root/site/docs/skylark
diff options
context:
space:
mode:
authorGravatar brandjon <brandjon@google.com>2018-03-26 08:53:02 -0700
committerGravatar Copybara-Service <copybara-piper@google.com>2018-03-26 08:54:48 -0700
commit22c573ca57cd62f6bdcf8f1619ff21e4af5516c0 (patch)
treebe56e5e81d88773f43c0ed16bbce8ff682caca79 /site/docs/skylark
parent1f8ba946a3c20413ff0a95235b20d7cc1b4964f0 (diff)
Fix typo in link
RELNOTES: None PiperOrigin-RevId: 190470599
Diffstat (limited to 'site/docs/skylark')
-rw-r--r--site/docs/skylark/faq.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/site/docs/skylark/faq.md b/site/docs/skylark/faq.md
index 8c8db05376..fcc32172a9 100644
--- a/site/docs/skylark/faq.md
+++ b/site/docs/skylark/faq.md
@@ -76,7 +76,7 @@ runfile to actions and executables that need it during the execution phase.
For rules and rule attributes, you can pass a docstring literal (possibly
triple-quoted) to the `doc` parameter of `rule` or `attr.*()`. For helper
functions and macros, use a triple-quoted docstring literal following the format
-given [here](skylint.md#docstings). Rule implementation functions generally do
+given [here](skylint.md#docstrings). Rule implementation functions generally do
not need their own docstring.
Using string literals in the expected places makes it easier for automated