docs: update docs for release

Author: alexeagle

docs/Built-ins.html

@@ -10,6 +10,7 @@ nav: rule
   Instead you must edit the .bzl file where the rules are declared,
   or possibly a markdown file next to the .bzl file
  ********************* -->
+
 # @bazel/concatjs
 
 Concatjs is a JavaScript bundler, in a trivial sense: the UNIX `cat` command is a basic implementation:
@@ -33,10 +34,8 @@ So Bazel rules that originated in Google's codebase have affordances for concatj
 For example `ts_library` produces named AMD modules in its "devmode" output, and
 `karma_web_test` expects to bundle inputs using concatjs.
 
-
 ## Compatibility
 
-
 ### First-party code
 
 First-party code has to be authored as named AMD/UMD modules.
@@ -59,7 +58,6 @@ using the TS triple-slash syntax:
 it is [also compiled with](https://github.com/bazelbuild/rules_nodejs/blob/bd53eb524ea3bd56b46b7a5f2eff700443e281ec/packages/concatjs/BUILD.bazel#L28)
 the `"compilerOptions": { "module": "umd" }` TypeScript setting.
 
-
 ### Third-party code
 
 To make it easier to produce a UMD version of a third-party npm package, we automatically generate a target that uses Browserify to build one, using the `main` entry from the package's `package.json`.
@@ -74,7 +72,6 @@ For example, even though RxJS ships with a UMD bundle, it contains multiple entr
 
 Ultimately by using concatjs, you're signing up for at least a superficial understanding of these shims and may need to update them when you change your dependencies.
 
-
 ## Serving JS in development mode under Bazel
 
 There are two choices for development mode:
@@ -131,7 +128,6 @@ finishes.
 
 [ibazel]: https://github.com/bazelbuild/bazel-watcher
 
-
 ## Testing with Karma
 
 The `karma_web_test` rule runs karma tests with Bazel.
@@ -160,7 +156,6 @@ browser_repositories(
 )
 ```
 
-
 ## Installing with user-managed dependencies
 
 If you didn't use the `yarn_install` or `npm_install` rule to create an `npm` workspace, you'll have to declare a rule in your root `BUILD.bazel` file to execute karma:
@@ -274,7 +269,6 @@ Defaults to `"/_/ts_scripts.js"`
 Defaults to `[]`
 
 
-
 ## karma_web_test
 
 **USAGE**
@@ -392,7 +386,6 @@ Passed through to `karma_web_test`
 
 
 
-
 ## karma_web_test_suite
 
 **USAGE**

docs/Built-ins.md

@@ -10,11 +10,11 @@ nav: rule
   Instead you must edit the .bzl file where the rules are declared,
   or possibly a markdown file next to the .bzl file
  ********************* -->
+
 # Cypress rules for Bazel
 
 The Cypress rules run tests under the Cypress e2e testing framework with Bazel.
 
-
 ## Installation
 
 Add `@bazel/cypress` and `cypress` npm packages to your `devDependencies` in `package.json`.
@@ -38,19 +38,16 @@ load("@npm//@bazel/cypress:index.bzl", "cypress_repository")
 cypress_repository(name = "cypress")
 ```
 
-
 ### macOS install requirements
 On macOS, `cypress_repository` generates an external repository containing files whose names contain spaces. In order to make these files compatible with bazel you will need to add the following flag to your `.bazelrc` file:
 ```python
 # Required for cypress_repository on macOS
 build --experimental_inprocess_symlink_creation
 ```
 
-
 ### windows install requirements
 At this point in time, `cypress_repository` is incompatible with bazel sandboxing on Windows. This may change in the future, but for now using cypress on windows requires windows sandboxing be disabled (it is disabled by default)
 
-
 ## Example use of cypress_web_test
 This example assumes you've named your external repository for node_modules as `npm` and for cypress as `cypress`
 ```python

docs/Concatjs.html

@@ -10,11 +10,11 @@ nav: rule
   Instead you must edit the .bzl file where the rules are declared,
   or possibly a markdown file next to the .bzl file
  ********************* -->
+
 # Jasmine rules for Bazel
 
 The Jasmine rules run tests under the Jasmine framework with Bazel.
 
-
 ## Installation
 
 Add the `@bazel/jasmine` npm package to your `devDependencies` in `package.json`.

docs/Concatjs.md

@@ -10,6 +10,7 @@ nav: rule
   Instead you must edit the .bzl file where the rules are declared,
   or possibly a markdown file next to the .bzl file
  ********************* -->
+
 # Bazel nodejs Labs
 
 This package contains experimental code which isn't at the same quality or stability standard as our main packages.