doc: fix markdown

  }

  ...

}

````

```

### `ng-publish` job

| `NPM_PUBLISH_REGISTRY`     | NPM registry to publish to | uses GitLab project npm packages registry  |

| :lock: `NPM_PUBLISH_TOKEN`     | NPM publication registry authentication token | none          |

:warning: When using the gitlab registry (which is the default behavior), your NPM package name must be in the format of `@scope/package-name`.

:warning: When using the gitlab registry (which is the default behavior), your NPM package name must be in the format of `@scope/package-name`:

* The `@scope` is the root namespace of the GitLab project. It must match exactly, including the case.

* The `package-name` can be whatever you want.

For example, if your project is `https://gitlab.example.com/my-org/engineering-group/team-amazing/analytics`, the root namespace is `my-org`. When you publish a package, it must have `my-org` as the scope.

For more details see [Package naming convention](https://docs.gitlab.com/ee/user/packages/npm_registry/#package-naming-convention).

:warning: Don't forget to specify the publication registry in the **project(s)** to publish `package.json` file (not the workspace top-level one).

```json

{

  "name": "@my-org/hello-world",

    "@my-org:registry": "https://<publication-registry-url>"

  }

}

```

:information_source: When using the GitLab registry, the registry publication url looks like `https://<gitlab-host>/api/v4/projects/<your_project_id>/packages/npm/`, with:

* `<gitlab-host>` is your GitLab host domain name.

* `<your_project_id>` is your project ID, **found on the project’s home page**.

#### Unit testing with Karma

##### Use an headless browser

```

In your `karma.conf.js`, add the plugin:

```js

  require('karma-sonarqube-execution-reporter')

```