Update documentation of skylark rules: correct load statements

Fixes #864.

--
MOS_MIGRATED_REVID=114208872

11 files changed, 46 insertions, 46 deletions

diff --git a/tools/build_defs/d/README.md b/tools/build_defs/d/README.md
index 3a7d503ba3..a099cc1665 100644
--- a/tools/build_defs/d/README.md
+++ b/tools/build_defs/d/README.md
@@ -19,7 +19,7 @@ To use the D rules, add the following to your `WORKSPACE` file to add the
 external repositories for the D toolchain:
 
 ```python
-load("/tools/build_defs/d/d", "d_repositories")
+load("@bazel_tools//tools/build_defs/d:d.bzl", "d_repositories")
 
 d_repositories()
 ```
@@ -136,7 +136,7 @@ The library `foo` is built using a `d_library` target:
 `foo/BUILD`:
 
 ```python
-load("/tools/build_defs/d/d", "d_library")
+load("@bazel_tools//tools/build_defs/d/d", "d_library")
 
 d_binary(
     name = "foo",
@@ -263,7 +263,7 @@ Build the C library using the `cc_library` rule and then use the
 `greeter/BUILD`:
 
 ```python
-load("/tools/build_defs/d/d", "d_source_library")
+load("@bazel_tools//tools/build_defs/d/d", "d_source_library")
 
 cc_library(
     name = "native_greeter_lib",
@@ -284,7 +284,7 @@ the C library:
 `hello_world/BUILD`:
 
 ```python
-load("/tools/build_defs/d/d", "d_source_library")
+load("@bazel_tools//tools/build_defs/d/d", "d_source_library")
 
 d_binary(
     name = "hello_world",
@@ -401,7 +401,7 @@ The `hello_lib` library is built using a `d_library` target:
 `hello_lib/BUILD`:
 
 ```python
-load("/tools/build_defs/d/d", "d_library")
+load("@bazel_tools//tools/build_defs/d/d", "d_library")
 
 d_library(
     name = "hello_lib",
@@ -425,7 +425,7 @@ The `hello_world` binary is built using a `d_binary` target:
 `hello_world/BUILD`:
 
 ```python
-load("/tools/build_defs/d/d", "d_library")
+load("@bazel_tools//tools/build_defs/d/d", "d_library")
 
 d_binary(
     name = "hello_world",
@@ -574,7 +574,7 @@ To build the library and unit test:
 `hello_lib/BUILD`:
 
 ```python
-load("/tools/build_defs/d/d", "d_library", "d_test")
+load("@bazel_tools//tools/build_defs/d/d", "d_library", "d_test")
 
 d_library(
     name = "greeter",
@@ -655,7 +655,7 @@ that takes the `d_library` `foo` as its dependency:
 `foo/BUILD`:
 
 ```python
-load("/tools/build_defs/d/d", "d_library", "d_docs")
+load("@bazel_tools//tools/build_defs/d/d", "d_library", "d_docs")
 
 d_library(
     name = "foo",
diff --git a/tools/build_defs/docker/README.md b/tools/build_defs/docker/README.md
index be0f120f97..33cbd5950f 100644
--- a/tools/build_defs/docker/README.md
+++ b/tools/build_defs/docker/README.md
@@ -30,7 +30,7 @@ The docker_build rule constructs a tarball that is compatible with
 Consider the following BUILD file in `//third_party/debian`:
 
 ```python
-load("/tools/build_defs/docker/docker", "docker_build")
+load("@bazel_tools//tools/build_defs/docker:docker.bzl", "docker_build")
 
 filegroup(
     name = "ca_certificates",
@@ -142,7 +142,7 @@ If you do not want to check in base image in your repository, you can use
 you could create various layer with `external` labels:
 
 ```python
-load("/tools/build_defs/docker/docker", "docker_build")
+load("@bazel_tools//tools/build_defs/docker:docker.bzl", "docker_build")
 
 docker_build(
     name = "java",
@@ -172,7 +172,7 @@ http_file(
 With the following `debian.BUILD` file:
 
 ```python
-load("/tools/build_defs/docker/docker", "docker_build")
+load("@bazel_tools//tools/build_defs/docker:docker.bzl", "docker_build")
 
 # Extract .xz files
 genrule(
diff --git a/tools/build_defs/dotnet/README.md b/tools/build_defs/dotnet/README.md
index 6c4369df64..36873ec411 100644
--- a/tools/build_defs/dotnet/README.md
+++ b/tools/build_defs/dotnet/README.md
@@ -23,7 +23,7 @@ might become especially valuable.
 Add the following to your `WORKSPACE` file to add the external repositories:
 
 ```python
-load("/tools/build_defs/dotnet/csharp", "csharp_repositories")
+load("@bazel_tools//tools/build_defs/dotnet:csharp.bzl", "csharp_repositories")
 
 csharp_repositories()
 ```
diff --git a/tools/build_defs/groovy/README.md b/tools/build_defs/groovy/README.md
index 09b35ecba2..a22bb05670 100644
--- a/tools/build_defs/groovy/README.md
+++ b/tools/build_defs/groovy/README.md
@@ -33,7 +33,7 @@ The easiest way to do so is to add the following to your `WORKSPACE` file and
 putting `groovy.BUILD` at the root of your workspace:
 
 ```python
-load("/tools/build_defs/groovy/groovy", "groovy_repositories")
+load("@bazel_tools//tools/build_defs/groovy:groovy.bzl", "groovy_repositories")
 
 groovy_repositories()
 ```
@@ -65,7 +65,7 @@ Then, to build the code under src/main/groovy/lib/, your
 `src/main/groovy/lib/BUILD` can look like this:
 
 ```python
-load("/tools/build_defs/groovy/groovy", "groovy_library")
+load("@bazel_tools//tools/build_defs/groovy:groovy.bzl", "groovy_library")
 
 groovy_library(
     name = "groovylib",
@@ -87,7 +87,7 @@ reference the Java code, but not vice-versa. Your `src/main/groovy/lib/BUILD`
 file would then look like this:
 
 ```python
-load("/tools/build_defs/groovy/groovy", "groovy_and_java_library")
+load("@bazel_tools//tools/build_defs/groovy:groovy.bzl", "groovy_and_java_library")
 
 groovy_and_java_library(
     name = "lib",
@@ -99,7 +99,7 @@ To build the application under src/main/groovy/app, you can define a binary
 using `groovy_binary` as follows:
 
 ```python
-load("/tools/build_defs/groovy/groovy", "groovy_binary")
+load("@bazel_tools//tools/build_defs/groovy:groovy.bzl", "groovy_binary")
 
 groovy_binary(
     name = "GroovyApp",
@@ -118,7 +118,7 @@ To build the test under src/test/groovy/lib, your BUILD file would look like
 this:
 
 ```python
-load("/tools/build_defs/groovy/groovy", "groovy_test", "groovy_library")
+load("@bazel_tools//tools/build_defs/groovy:groovy.bzl", "groovy_test", "groovy_library")
 
 
 groovy_library(
diff --git a/tools/build_defs/jsonnet/README.md b/tools/build_defs/jsonnet/README.md
index afdea804f8..59db1888c8 100644
--- a/tools/build_defs/jsonnet/README.md
+++ b/tools/build_defs/jsonnet/README.md
@@ -21,7 +21,7 @@ To use the Jsonnet rules, add the following to your `WORKSPACE` file to add the
 external repositories for Jsonnet:
 
 ```python
-load("/tools/build_defs/jsonnet/jsonnet", "jsonnet_repositories")
+load("@bazel_tools//tools/build_defs/jsonnet:jsonnet.bzl", "jsonnet_repositories")
 
 jsonnet_repositories()
 ```
@@ -103,7 +103,7 @@ files that can be imported by other `.jsonnet` files as dependencies:
 `configs/BUILD`:
 
 ```python
-load("/tools/build_defs/jsonnet/jsonnet", "jsonnet_library")
+load("@bazel_tools//tools/build_defs/jsonnet:jsonnet.bzl", "jsonnet_library")
 
 jsonnet_library(
     name = "configs",
@@ -266,7 +266,7 @@ First, create a `jsonnet_library` target with `workflow.jsonnet`:
 `workflows/BUILD`:
 
 ```python
-load("/tools/build_defs/jsonnet/jsonnet", "jsonnet_library")
+load("@bazel_tools//tools/build_defs/jsonnet:jsonnet.bzl", "jsonnet_library")
 
 jsonnet_library(
     name = "workflow",
@@ -483,7 +483,7 @@ the expected JSON output:
 
 ```python
 load(
-    "/tools/build_defs/jsonnet/jsonnet",
+    "@bazel_tools//tools/build_defs/jsonnet:jsonnet.bzl",
     "jsonnet_library",
     "jsonnet_to_json_test",
 )
@@ -531,7 +531,7 @@ the expected error output:
 
 ```python
 load(
-    "/tools/build_defs/jsonnet/jsonnet",
+    "@bazel_tools//tools/build_defs/jsonnet:jsonnet.bzl",
     "jsonnet_library",
     "jsonnet_to_json_test",
 )
diff --git a/tools/build_defs/pkg/README.md b/tools/build_defs/pkg/README.md
index 31e6862a50..c2649352db 100644
--- a/tools/build_defs/pkg/README.md
+++ b/tools/build_defs/pkg/README.md
@@ -20,7 +20,7 @@ This example is a simplification of the debian packaging of Bazel:
 
 ```python
 
-load("/tools/build_defs/pkg/pkg", "pkg_tar", "pkg_deb")
+load("@bazel_tools//tools/build_defs/pkg:pkg.bzl", "pkg_tar", "pkg_deb")
 
 pkg_tar(
     name = "bazel-bin",
diff --git a/tools/build_defs/sass/README.md b/tools/build_defs/sass/README.md
index ee4b65cc9c..5e7d7217ef 100644
--- a/tools/build_defs/sass/README.md
+++ b/tools/build_defs/sass/README.md
@@ -19,7 +19,7 @@ To  use the Sass rules, add the following to your `WORKSPACE` file to add the
 external repositories for Sass:
 
 ```python
-load("/tools/build_defs/sass/sass", "sass_repositories")
+load("@bazel_tools//tools/build_defs/sass:sass.bzl", "sass_repositories")
 
 sass_repositories()
 ```
@@ -62,7 +62,7 @@ $example-red: #ff0000;
 ```python
 package(default_visibility = ["//visibility:public"])
 
-load("/tools/build_defs/sass/sass", "sass_library")
+load("@bazel_tools//tools/build_defs/sass:sass.bzl", "sass_library")
 
 sass_library(
     name = "colors",
@@ -97,7 +97,7 @@ html {
 ```python
 package(default_visibility = ["//visibility:public"])
 
-load("/tools/build_defs/sass/sass", "sass_binary")
+load("@bazel_tools//tools/build_defs/sass:sass.bzl", "sass_binary")
 
 sass_binary(
     name = "hello_world",
diff --git a/tools/build_rules/appengine/README.md b/tools/build_rules/appengine/README.md
index 3477c61586..0b047c9203 100644
--- a/tools/build_rules/appengine/README.md
+++ b/tools/build_rules/appengine/README.md
@@ -23,7 +23,7 @@ available to Bazel. The easiest way to do so is by adding the following to your
 `WORKSPACE` file:
 
 ```python
-load("/tools/build_rules/appengine/appengine", "appengine_repositories")
+load("@bazel_tools//tools/build_rules/appengine:appengine.bzl", "appengine_repositories")
 
 appengine_repositories()
 ```
@@ -51,7 +51,7 @@ application:
 Then, to build your webapp, your `hello_app/BUILD` can look like:
 
 ```python
-load("/tools/build_rules/appengine/appengine", "appengine_war")
+load("@bazel_tools//tools/build_rules/appengine:appengine.bzl", "appengine_war")
 
 java_library(
     name = "mylib",
@@ -74,7 +74,7 @@ For simplicity, you can use the `java_war` rule to build an app from source.
 Your `hello_app/BUILD` file would then look like:
 
 ```python
-load("/tools/build_rules/appengine/appengine", "java_war")
+load("@bazel_tools//tools/build_rules/appengine:appengine.bzl", "java_war")
 
 java_war(
     name = "myapp",
diff --git a/tools/build_rules/closure/README.md b/tools/build_rules/closure/README.md
index fc4633fd24..9593b815c3 100644
--- a/tools/build_rules/closure/README.md
+++ b/tools/build_rules/closure/README.md
@@ -16,7 +16,7 @@ Add the following to your `WORKSPACE` file to add the external repositories
 for the various Closure Tools binaries and the Closure Library:
 
 ```python
-load("/tools/build_rules/closure/closure_repositories", "closure_repositories")
+load("@bazel_tools//tools/build_rules/closure:closure_repositories.bzl", "closure_repositories")
 
 closure_repositories()
 ```
@@ -67,10 +67,10 @@ We can create a BUILD file to compile these and produce two files:
 `BUILD`
 
 ```python
-load("/tools/build_rules/closure/closure_js_binary", "closure_js_binary")
-load("/tools/build_rules/closure/closure_js_library", "closure_js_library")
-load("/tools/build_rules/closure/closure_stylesheet_library", "closure_stylesheet_library")
-load("/tools/build_rules/closure/closure_template_library", "closure_template_library")
+load("@bazel_tools//tools/build_rules/closure:closure_js_binary.bzl", "closure_js_binary")
+load("@bazel_tools//tools/build_rules/closure:closure_js_library.bzl", "closure_js_library")
+load("@bazel_tools//tools/build_rules/closure:closure_stylesheet_library.bzl", "closure_stylesheet_library")
+load("@bazel_tools//tools/build_rules/closure:closure_template_library.bzl", "closure_template_library")
 
 closure_js_binary(
     name = "hello",
diff --git a/tools/build_rules/go/README.md b/tools/build_rules/go/README.md
index b649fe0e33..535c2a487a 100644
--- a/tools/build_rules/go/README.md
+++ b/tools/build_rules/go/README.md
@@ -34,7 +34,7 @@ They currently do not support (in order of importance):
 * Add the following to your WORKSPACE file:
 
     ```python
-    load("/tools/build_rules/go/def", "go_repositories")
+    load("@bazel_tools//tools/build_rules/go:def.bzl", "go_repositories")
 
     go_repositories()
     ```
@@ -44,7 +44,7 @@ They currently do not support (in order of importance):
   empty.
 
     ```python
-    load("/tools/build_rules/go/def", "go_prefix")
+    load("@bazel_tools//tools/build_rules/go:def.bzl", "go_prefix")
 
     go_prefix("github.com/joe/project")
     ```
@@ -52,7 +52,7 @@ They currently do not support (in order of importance):
 * For a library `github.com/joe/project/lib`, create `lib/BUILD`, containing
 
     ```python
-    load("/tools/build_rules/go/def", "go_library")
+    load("@bazel_tools//tools/build_rules/go:def.bzl", "go_library")
 
     go_library(
         name = "go_default_library",
diff --git a/tools/build_rules/rust/README.md b/tools/build_rules/rust/README.md
index f6f0dc0c16..85b9978ee7 100644
--- a/tools/build_rules/rust/README.md
+++ b/tools/build_rules/rust/README.md
@@ -25,7 +25,7 @@ To use the Rust rules, add the following to your `WORKSPACE` file to add the
 external repositories for the Rust toolchain:
 
 ```python
-load("/tools/build_rules/rust/rust", "rust_repositories")
+load("@bazel_tools//tools/build_rules/rust:rust.bzl", "rust_repositories")
 
 rust_repositories()
 ```
@@ -192,7 +192,7 @@ pub mod greeter;
 ```python
 package(default_visibility = ["//visibility:public"])
 
-load("/tools/build_rules/rust/rust", "rust_library")
+load("@bazel_tools//tools/build_rules/rust:rust.bzl", "rust_library")
 
 rust_library(
     name = "hello_lib",
@@ -360,7 +360,7 @@ impl Greeter {
 ```python
 package(default_visibility = ["//visibility:public"])
 
-load("/tools/build_rules/rust/rust", "rust_library")
+load("@bazel_tools//tools/build_rules/rust:rust.bzl", "rust_library")
 
 rust_library(
     name = "hello_lib",
@@ -382,7 +382,7 @@ fn main() {
 `hello_world/BUILD`:
 
 ```python
-load("/tools/build_rules/rust/rust", "rust_binary")
+load("@bazel_tools//tools/build_rules/rust:rust.bzl", "rust_binary")
 
 rust_binary(
     name = "hello_world",
@@ -560,7 +560,7 @@ only depends on the `hello_lib` `rust_library` target:
 ```python
 package(default_visibility = ["//visibility:public"])
 
-load("/tools/build_rules/rust/rust", "rust_library", "rust_test")
+load("@bazel_tools//tools/build_rules/rust:rust.bzl", "rust_library", "rust_test")
 
 rust_library(
     name = "hello_lib",
@@ -617,7 +617,7 @@ with `greeting.rs` in `srcs` and a dependency on the `hello_lib` target:
 ```python
 package(default_visibility = ["//visibility:public"])
 
-load("/tools/build_rules/rust/rust", "rust_library", "rust_test")
+load("@bazel_tools//tools/build_rules/rust:rust.bzl", "rust_library", "rust_test")
 
 rust_library(
     name = "hello_lib",
@@ -804,7 +804,7 @@ To build the benchmark test, simply add a `rust_bench_test` target:
 ```python
 package(default_visibility = ["//visibility:public"])
 
-load("/tools/build_rules/rust/rust", "rust_library", "rust_bench_test")
+load("@bazel_tools//tools/build_rules/rust:rust.bzl", "rust_library", "rust_bench_test")
 
 rust_library(
     name = "fibonacci",
@@ -913,7 +913,7 @@ a `rust_doc` rule that depends on the the `hello_lib` `rust_library` target:
 ```python
 package(default_visibility = ["//visibility:public"])
 
-load("/tools/build_rules/rust/rust", "rust_library", "rust_doc")
+load("@bazel_tools//tools/build_rules/rust:rust.bzl", "rust_library", "rust_doc")
 
 rust_library(
     name = "hello_lib",
@@ -991,7 +991,7 @@ To run [documentation tests][doc-test] for the `hello_lib` crate, define a
 ```python
 package(default_visibility = ["//visibility:public"])
 
-load("/tools/build_rules/rust/rust", "rust_library", "rust_doc_test")
+load("@bazel_tools//tools/build_rules/rust:rust.bzl", "rust_library", "rust_doc_test")
 
 rust_library(
     name = "hello_lib",