Permalink
Browse files

Docs: Fix some links

  • Loading branch information...
sarvaje authored and molant committed Nov 29, 2018
1 parent 1c0785e commit f72dbccc868b0840d93a50fd2b4bc3e19a702b76
@@ -40,7 +40,7 @@ their signature, and the `interface` they implement. The exception is the
* [`traverse::end`](#traverseend)
* [`traverse::start`](#traversestart)
* [`traverse::up`](#traverseup)
* [`can-evaluate::script`](#canevaluatescript)
* [`can-evaluate::script`](#can-evaluatescript)

For additional events emitted by specific `parser`s (e.g. `parse::end::css`),
see [`parsers`][parsers].
@@ -212,7 +212,7 @@ type TraverseUp {
}
```

## `can-evaluate`
## `can-evaluate::script`

Event is emitted **when** the `connector` is ready to evaluate
scripts.
@@ -186,7 +186,7 @@ push instead:
git push -f origin fix-1234
```

### Step 7: Send the pull request
### Step 7: Submit the pull request

Now you’re ready to send the pull request. Go to your `webhint` fork
and then follow the [GitHub documentation][github pr docs] on how to
@@ -135,8 +135,8 @@ following tests:
[jsdom]: https://github.com/jsdom/jsdom
[events]: ../getting-started/events.md
[events scanstart]: ../getting-started/events.md#scanstart
[events fetchstart]: ../getting-started/events.md#fetchstart
[events fetcherror]: ../getting-started/events.md#fetcherror
[events fetchstart]: ../getting-started/events.md#fetchstartresource-type
[events fetcherror]: ../getting-started/events.md#fetcherrorresource-type
[events fetchend]: ../getting-started/events.md#fetchendresource-type
[events traversestart]: ../getting-started/events.md#traversestart
[events element]: ../getting-started/events.md#elementelement-type
@@ -34,7 +34,7 @@ The current supported connectors are:
[`edge-diagnostics-adapter`][eda]. You will need to run Windows 10
Creators Update or later to use it. This connector will only be
installed if you are running on it. There are some known issues so
please check the [Edge issues](#edge-issues) section below.
please check the [Edge issues](#edge) section below.
* `local`: This connector will analyze the files specified (a file
or a directory).

@@ -85,7 +85,7 @@ Depending on the `connector`, other configurations may be available.

<!-- markdownlint-disable MD033 -->

### remote-debugging-connector configuration <a name="rdc-config"></a>
### remote-debugging-connector configuration

<!-- markdownlint-enable MD033 -->

@@ -160,7 +160,7 @@ connectors.

<!-- markdownlint-disable MD033 -->

### Edge<a name="edge-issues"></a>
### Edge

<!-- markdownlint-enable MD033 -->

@@ -36,4 +36,4 @@ browserslist.defaults = [

[browserslist]: https://github.com/ai/browserslist#readme
[browserslist defaults]: https://github.com/ai/browserslist#queries
[doc modes]: https://webhint.io/docs/hints/hint-highest-available-document-mode/
[doc modes]: https://webhint.io/docs/user-guide/hints/hint-highest-available-document-mode/
@@ -18,4 +18,4 @@ There are a couple things to take into account:

<!-- Link labels: -->

[chrome configuration]: ../concepts/connectors.md#rdc-config
[chrome configuration]: ../concepts/connectors.md#remote-debugging-connector-configuration
@@ -75,7 +75,7 @@ Wait a few seconds and you will get something similar to the following:
![Example output for the summary formatter](images/summary-output.png)

It might take a few minutes to get some of the results. Some of the
hints (e.g.: [`SSL Labs`](./hints/hint-ssllabs.md)) can take a few minutes
hints (e.g.: [`SSL Labs`][ssl labs]) can take a few minutes
to report the results.

### Default configuration
@@ -105,3 +105,4 @@ about the different pieces:

[nodejs]: https://nodejs.org/en/download/current/
[web recommended]: https://github.com/webhintio/hint/blob/master/packages/configuration-web-recommended/index.json
[ssl labs]: https://webhint.io/docs/user-guide/hints/hint-ssllabs/

0 comments on commit f72dbcc

Please sign in to comment.