webhintio · IAmHopp · Aug 7, 2018 · Aug 7, 2018 · Aug 7, 2018 · Aug 7, 2018
@@ -1,3 +1,10 @@
+# 1.0.1 (August 7, 2018)
+
+## Bug fixes / Improvements
+
+* [[`a685a314c2`](https://github.com/webhintio/hint/commit/a685a314c277235a5df9156ef925be49bbccdafd)] - Fix: Remove `no-broken-links` hint (by [`Cătălin Mariș`](https://github.com/alrra)).
+
+
 # 1.0.0 (August 7, 2018)
 
 ✨
@@ -19,7 +19,6 @@
         "meta-charset-utf-8": "error",
         "meta-viewport": "error",
         "no-bom": "error",
-        "no-broken-links": "error",
         "no-disallowed-headers": "error",
         "no-friendly-error-pages": "error",
         "no-html-only-headers": "error",

@@ -16,7 +16,6 @@
     "@hint/hint-meta-charset-utf-8": "^1.0.0",
     "@hint/hint-meta-viewport": "^1.0.0",
     "@hint/hint-no-bom": "^1.0.0",
-    "@hint/hint-no-broken-links": "^1.0.2",
     "@hint/hint-no-disallowed-headers": "^1.0.0",
     "@hint/hint-no-friendly-error-pages": "^1.0.0",
     "@hint/hint-no-html-only-headers": "^1.0.0",
@@ -55,5 +54,5 @@
     "hint": "^3.0.1"
   },
   "repository": "webhintio/hint",
-  "version": "1.0.0"
+  "version": "1.0.1"
 }
@@ -22,8 +22,8 @@ HTML of your page.
 
 Yes, you can decide if you want to receive errors only, or also
 warnings found by [`amphtml-validator`][amphtml-validator].
-By default all warnings and errors are reported. If you prefer to
-see only the errors you can use the following hint configuration
+By default, all warnings and errors are reported. If you prefer to
+see only the errors, you can use the following hint configuration
 in your [`.hintrc`][hintrc] file:
 
 ```json

@@ -5,14 +5,14 @@
 
 ## Why is this important?
 
-Since `iOS 1.1.3` Safari for iOS has supported a way for developers
+Since `iOS 1.1.3`, Safari for iOS has supported a way for developers
 to specify an image that will be used to represent the web site/app
-on the homescreen. The image is known as the [touch icon][touch icons].
+on the home screen. The image is known as the [touch icon][touch icons].
 
-Note: As of `iOS 11.1.0` Safari for iOS [supports the web app manifest
+Note: As of `iOS 11.1.0`, Safari for iOS [supports the web app manifest
 file][safari 11.1] which provides a standard, cross-browser way of
 defining, among other, the icons browsers can use in various contexts
-(homescreen, application menu, etc.). However, Safari ignores the icons
+(home screen, application menu, etc.). However, Safari ignores the icons
 defined in the web app manifest and still uses the non-standard
 `apple-touch-icon`.
 
@@ -40,13 +40,13 @@ sizes is not recommended as:
 
 * It will increase the size of the pages with very little to no
   real benefit (most users will probably not add the site to their
-  homescreens).
+  home screens).
 
 * Most sizes will probably never be used as iOS devices get upgraded
-  pretty quickly, so [most iOS users will be on the latest 2 versions
-  of iOS][app store stats], and using newer devices.
+  quickly, so [most iOS users will be on the latest 2 versions
+  of iOS][app store stats] and using newer devices.
 
-* The `180×180px` image, if needed, [will be automatically down scaled
+* The `180×180px` image, if needed, [will be automatically downscaled
   by Safari, and the result of the scaling is generally ok][icon
   scaling].
 
@@ -57,11 +57,11 @@ as users upgrade their devices and their iOS version.
 
 Other notes:
 
-* Not declaring the touch icon in the page, and having it in the
+* Not declaring the touch icon in the page and having it in the
   root of the site is not recommended as [Apple usually changes
   what is requested by default][h5bp issue 1622].
 
-* In older versions of Safari for iOS the [`precomposed` keyword][icon
+* In older versions of Safari for iOS, the [`precomposed` keyword][icon
   effects] could be used to prevent iOS from adding different visual
   effects to the touch icon (i.e. rounded corners, drop shadow,
   reflective shine). Starting with iOS 7 no special effects are applied
@@ -75,12 +75,12 @@ Other notes:
 ## What does the hint check?
 
 The hint checks if a single `apple-touch-icon` declaration exists in
-the `<head>`, and it:
+the `<head>`, and:
 
-* has `rel="apple-touch-icon"`
+* it has `rel="apple-touch-icon"`
 * the declared image is accessible (e.g.: doesn’t result in a `404`),
   a `PNG`, and its size is `180×180px`
-* does not include the `sizes` attribute
+* it does not include the `sizes` attribute
 
 ### Examples that **trigger** the hint
 

@@ -24,14 +24,14 @@ Web impacts the lives of people with disabilities, the overlap with
 digital divide issues, and Web accessibility as an aspect of corporate
 social responsibility.
 >
-> Another important consideration for organizations is that web i
+> Another important consideration for organizations is that web
 accessibility is required by laws and policies in some cases.
 
 ***From [WAI’s Introduction to Web Accessibility][wai].***
 
 ## What does the hint check?
 
-By default this hint runs all the [WCAG 2.0][wcag 2.0] Level A and
+By default, this hint runs all the [WCAG 2.0][wcag 2.0] Level A and
 Level AA rules included in [axe-core][axe core] with `document` as
 the target. Visit the [full list of default enabled rules][axe rules]
 for more information of what they do.
@@ -133,7 +133,7 @@ And then activate it via the [`.hintrc`][hintrc] configuration file:
 
 ## Further Reading
 
-* [Deque Univeristy](https://dequeuniversity.com/)
+* [Deque University](https://dequeuniversity.com/)
 * [aXe core GitHub page][axe core]
 * [Web Accessibility Initiative (WAI)](https://www.w3.org/WAI/)
 

@@ -24,7 +24,7 @@ charset for the response as, among other:
 ## What does the hint check?
 
 The hint checks if responses include the `Content-Type` HTTP response
-header and its value contains the appropiate media type and charset
+header and its value contains the appropriate media type and charset
 for the response.
 
 ### Examples that **trigger** the hint

@@ -13,7 +13,7 @@ Links that have `target="_blank"`, such as
 
 * [a security problem][security problem]
 
-  When using `target="_blank"` the page that was linked to gains
+  When using `target="_blank"`, the page that was linked to gains
   access to the original page’s [`window.opener`][window.opener].
   This allows it to redirect the original page to whatever it wants,
   a technique frequently used for malicious attacks on the user.
@@ -27,9 +27,9 @@ Links that have `target="_blank"`, such as
 
 * [a performance problem][performance problem]
 
-  Most modern browsers are multi-process. However, due to the
-  synchronous cross-window access the DOM allows via `window.opener`,
-  in most browsers pages launched via `target="_blank"` end up in
+  Most modern browsers are multi-process. However, in most browsers,
+  due to the synchronous cross-window access the DOM allows via
+  `window.opener`, pages launched via `target="_blank"` end up in
   the same process as the origin page, and that can lead to the pages
   experiencing jank.
 
@@ -43,7 +43,7 @@ Links that have `target="_blank"`, such as
 Notes:
 
 * Not all browsers [support][noopener support] `rel="noopener"`,
-  so in order to ensure that things work as expected in as many
+  so to ensure that things work as expected in as many
   browsers as possible, by default, the hint requires both the
   `noopener` and `noreferrer` values to be specified. However,
   if all the [targeted browsers](../index.md#browser-configuration)
@@ -54,8 +54,8 @@ Notes:
 
   * Security isn’t really a problem here.
   * When it comes to performance, making same origin links open in
-    their own process actually works against optimizations that some
-    browsers do in order to keep multiple same origin tabs within
+    their own process works against optimizations that some
+    browsers do to keep multiple same origin tabs within
     the same process (e.g. share the same event loop).
 
   Check [`Can the hint be configured?`](#can-the-hint-be-configured)
@@ -66,7 +66,7 @@ Notes:
   elements][html5sec].
 
 * In the future there may be a [CSP valueless property][csp valueless
-  property] property that will prevent the `window.opener` reference
+  property] that will prevent the `window.opener` reference
   from being set.
 
 ## What does the hint check?

@@ -46,7 +46,7 @@ Notes:
 
 ## What does the hint check?
 
-By default the hint checks if the `X-UA-Compatible` response header is
+By default, the hint checks if the `X-UA-Compatible` response header is
 sent with the value of `IE=edge`, and that the `meta` tag isn’t used.
 
 ### Examples that **trigger** the hint for defaults
@@ -361,7 +361,7 @@ In the [`.hintrc`][hintrc] file:
 
 Also, note that this hint takes into consideration the [targeted
 browsers][targeted browsers], and if Internet Explorer 8/9/10 aren’t
-among them, it will suggest removing the `meta` tag or/and not sending
+among them, it will suggest removing the `meta` tag and/or not sending
 the HTTP response header.
 
 ## How to use this hint?
@@ -416,4 +416,5 @@ And then activate it via the [`.hintrc`][hintrc] configuration file:
 [mod_mime]: https://httpd.apache.org/docs/current/mod/mod_mime.html
 
 <!-- IIS Links -->
+
 [url rewrite]: https://docs.microsoft.com/en-us/iis/extensions/url-rewrite-module/using-the-url-rewrite-module
@@ -11,15 +11,15 @@
 > Adhering to the W3C’s standards has a lot to offer to both the
 > developers and the web users: It provides better browser compatibility,
 > helps to avoid potential problems with accessibility/usability,
-> and makes it easier for future maintainance.
+> and makes it easier for future maintenance.
 >
 > The Nu Html Checker(v.Nu) serves as the backend of
 > [html5.validator.nu][html5 validator], and
 > [validator.w3.org/nu][w3 validator].
 > It also provides a [web service interface][validator interface].
 
-This hint interacts with this service via [`request`][request],
-and is able to test both remote websites and local server instances.
+This hint interacts with this service via [`request`][request]
+and can test both remote websites and local server instances.
 
 ## What does the hint check?
 
@@ -36,14 +36,14 @@ the positive cases contain two sections:
   behavior—so that, say, you’d end up with some unintuitive, unexpected
   result in the DOM.
 
-For explanation behind those requirements, please checkout:
+For explanation behind those requirements, please check out:
 
 * [rationale for syntax-level errors](https://www.w3.org/TR/html/introduction.html#syntax-errors)
 * [rationale for restrictions on content models and on attribute values](https://www.w3.org/TR/html/introduction.html#restrictions-on-content-models-and-on-attribute-values)
 
 ## Can the hint be configured?
 
-By default only the first occurance of each error/warning is reported
+By default, only the first occurrence of each error/warning is reported
 when validating the markup. However, you can configure the hint to view
 the complete list.
 
@@ -87,7 +87,7 @@ the message of `Invalid attribute`:
 ```
 
 Alternative, you can pass in an array if you have more than one type
-of messages to ignore:
+of message to ignore:
 
 ```json
 {

@@ -30,9 +30,9 @@ validate that the page and resources have a good caching strategy:
 * static resources such as JavaScript, CSS, images, etc.:
   * have a long expiry value (>= 1 year)
   * use the `immutable` directive
-  * follow some kind of filename/path based revving, and not
+  * follow filename/path-based revving, and not
     one based on query string parameters (see: [problems with
-    proxys][revving files])
+    proxies][revving files])
 
 The built-in regular expressions for file revving are:
 
@@ -153,7 +153,7 @@ Cache-Control: max-age=31536000, immutable
 ...
 ```
 
-A page with `no-cache` :
+A page with `no-cache`:
 
 ```text
 HTTP/... 200 OK
@@ -219,7 +219,7 @@ Important notes:
         #     of a `.htaccess` file where only the `<Files>` directive
         #     can be used, reason why the best that can be done is match
         #     all files named `favicon.ico` (but that should work fine
-        #     if filename/path based revving is used)
+        #     if filename/path-based revving is used)
         #
         # See also: https://httpd.apache.org/docs/current/sections.html#file-and-web.
 
@@ -276,7 +276,7 @@ Also note that:
 * The above snippet works with Apache `v2.2.0+`, but you need to
   have [`mod_expires`][mod_expires] and [`mod_headers`][mod_headers]
   [enabled][how to enable apache modules]
-  in order for it to take effect.
+  for it to take effect.
 
 * If you have access to the [main Apache configuration file][main
   apache conf file] (usually called `httpd.conf`), you should add
@@ -321,8 +321,8 @@ with `cache-control: max-age=31536000, immutable`:
 </configuration>
 ```
 
-In the example above you want to have your JavaScript, CSS, images, etc.
-under the `static` folder, and your HTML elesewhere. If your static
+In the example above, you want to have your JavaScript, CSS, images, etc.
+under the `static` folder, and your HTML elsewhere. If your static
 content is in another folder change the path of `<location path="static">`
 to the right one.
 
@@ -346,7 +346,7 @@ Yes, you can configure:
 
 ### `max-age`
 
-By default the recommended value for the page is `Cache-Control: no-cache`
+By default, the recommended value for the page is `Cache-Control: no-cache`
 or a `max-age` equal or less to 3 minutes. For the resources `max-age` should
 be greater or equal to 1 year. You can change this as follows:
 
@@ -359,11 +359,11 @@ be greater or equal to 1 year. You can change this as follows:
 
 ### Custom regular expressions for revving files
 
-If none on the built-in regular expressions work for your use case, you
+If none of the built-in regular expressions work for your use case, you
 can provide your own via the `revvingPatterns` property. This property
 accepts an `Array` of escaped `RegExp`:
 
-in then [`.hintrc`][hintrc] file:
+in the [`.hintrc`][hintrc] file:
 
 ```json
 
@@ -381,7 +381,7 @@ in then [`.hintrc`][hintrc] file:
 ```
 
 Also pay attention to the escaping. The example above will validate
-that static resources follow a convention similar to the following
+that static resources follow a convention like the following
 one:
 
 ```text