Fix a bad path and remove the reference to the legacy path-based load…

…() syntax.

RELNOTES: None.
PiperOrigin-RevId: 200379060

src/main/java/com/google/devtools/build/docgen/templates/be/functions.vm

@@ -72,7 +72,7 @@ This will make <code>COMPILER_FLAGS</code> exported from
 
 <p>
   The label must refer to an existing package. For example, for the above
-  statement to work, <code>tools/build_rules/BUILD</code> must exist (an empty
+  statement to work, <code>path/to/rules/BUILD</code> must exist (an empty
   file is sufficient) The name of the file must have the suffix
   <code>.bzl</code>. If the specified label is in the relative label syntax
   (<code>:a/b.bzl</code>), it will be resolved relative to the package of the
@@ -81,20 +81,6 @@ This will make <code>COMPILER_FLAGS</code> exported from
   to make the <code>.bzl</code> file visible.
 </p>
 
-<p>
-  Note: The <code>load</code> statement still supports the legacy syntax that refers
-  to Skylark modules by their paths and not by their labels. This statement is
-  equivalent to the first example:
-</p>
-
-<pre class="code">
-load("/tools/build_rules/build_test", "build_test")
-</pre>
-
-<p>
-  However, this syntax is deprecated and will be removed soon.
-</p>
-
 <!-- =================================================================
                               package()
      =================================================================