@@ -74,8 +74,8 @@ This plug-in is **not** available on the API of remark.
7474
7575You can pass a `repository`, containing anything `package.json`s
7676[`repository`][package-repository] can handle. If this is omitted,
77−**remark-validate-links** will try the `package.json` in your
78−current working directory.
77+`remark-validate-links` will try the `package.json` in your current working
78+directory.
7979
8080```bash
8181remark --use 'validate-links=repository:"foo/bar"' example.md
@@ -103,17 +103,16 @@ An example `.remarkrc` file could look as follows:
103103**remark-validate-links** can detect anchors on nodes through
104104several properties on nodes:
105105
106−* `node.data.htmlAttributes.name` — Used by [`remark-html`][remark-html]
107− to create a `name` attribute, which anchors can link to;
108−* `node.data.htmlAttributes.id` — Used by [`remark-html`][remark-html]
109− to create an `id` attribute, which anchors can link to;
106+* `node.data.hProperties.name` — Used by [`remark-html`][remark-html]
107+ to create a `name` attribute, which anchors can link to
108+* `node.data.hProperties.id` — Used by [`remark-html`][remark-html]
109+ to create an `id` attribute, which anchors can link to
110110* `node.data.id` — Used, in the future, by other tools to signal
111− unique identifiers on nodes.
111+ unique identifiers on nodes
112112
113113## Related
114114
115−* [`wooorm/remark-lint`][remark-lint]
116− — Markdown code style linter.
115+* [`remark-lint`][remark-lint] — Markdown code style linter
117116
118117## License
119118