diff options
author | 2016-07-26 15:52:48 +0000 | |
---|---|---|
committer | 2016-07-27 11:14:46 +0000 | |
commit | 89100870293e5ba00eddcf470a1dbb6c3ca309b8 (patch) | |
tree | 735b3e507310620c2cb57a1e51394da5bdcbd302 /site/docs/skylark/rules.md | |
parent | 3b16a284b202e410d3b1bc9b14a578773e530b18 (diff) |
Typo fixes in markdown and javadoc as suggested by intellij typo inspection.
--
MOS_MIGRATED_REVID=128476121
Diffstat (limited to 'site/docs/skylark/rules.md')
-rw-r--r-- | site/docs/skylark/rules.md | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/site/docs/skylark/rules.md b/site/docs/skylark/rules.md index c2f191423f..809b8763da 100644 --- a/site/docs/skylark/rules.md +++ b/site/docs/skylark/rules.md @@ -37,7 +37,7 @@ A custom rule can be used just like a native rule. It has a mandatory `name` attribute, you can refer to it with a label, and you can see it in `bazel query`. -The rule is analyzed when you explictly build it, or if it is a dependency of +The rule is analyzed when you explicitly build it, or if it is a dependency of the build. In this case, Bazel will execute its `implementation` function. This function decides what the outputs of the rule are and how to build them (using `actions`). During analysis, no external command can be executed: actions will @@ -327,7 +327,7 @@ def rule_implementation(ctx): ``` A dependent rule might access these data as struct fields of the `target` being -dependened upon: +depended upon: ```python def dependent_rule_implementation(ctx): |