aboutsummaryrefslogtreecommitdiffhomepage
path: root/site
diff options
context:
space:
mode:
authorGravatar Tyler True <t.to.the.square@gmail.com>2017-11-29 02:04:09 -0800
committerGravatar Copybara-Service <copybara-piper@google.com>2017-11-29 02:06:04 -0800
commit373621188dd1a30508d197735d1a4137cf300798 (patch)
tree8854b66840288d7c914196d227723e4c1afe04ba /site
parentefdb1a73edd66d8dfb3afffbc9766433ca889725 (diff)
Docs: (minor) Change "chaiscript" to "mockascript"
Avoids ambiguity; "chaiscript" is a real language. (See http://chaiscript.com ) Satisfies (unreported issue): https://twitter.com/lefticus/status/932423849928519681 Resolves #4133. Closes #4125. PiperOrigin-RevId: 177281798
Diffstat (limited to 'site')
-rw-r--r--site/docs/skylark/deploying.md12
1 files changed, 6 insertions, 6 deletions
diff --git a/site/docs/skylark/deploying.md b/site/docs/skylark/deploying.md
index 912e7dd1e0..91312ca420 100644
--- a/site/docs/skylark/deploying.md
+++ b/site/docs/skylark/deploying.md
@@ -39,24 +39,24 @@ Every rule repository should have a certain layout so that users can quickly
understand new rules.
For example, suppose we are writing new Skylark rules for the (make-believe)
-chaiscript language. We would have the following structure:
+mockascript language. We would have the following structure:
```
.travis.yml
README.md
WORKSPACE
-chaiscript/
+mockascript/
BUILD
- chaiscript.bzl
+ mockascript.bzl
tests/
BUILD
some_test.sh
another_test.py
examples/
BUILD
- bin.chai
- lib.chai
- test.chai
+ bin.mocs
+ lib.mocs
+ test.mocs
```
### README.md