This repository was archived by the owner on Feb 24, 2021. It is now read-only.
File tree Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Expand file tree Collapse file tree 1 file changed +4
-4
lines changed Original file line number Diff line number Diff line change @@ -302,11 +302,11 @@ The following opt-in flags are available:
302
302
The test validates the links in markdown files. Any valid GitHub markdown link
303
303
will pass the linter.
304
304
305
- > ** NOTE!** There are currently a bug in the markdown link linter that makes it
306
- > unable to recognized absolute paths where the absolute link starts in a parent
305
+ > ** NOTE!** There is currently a bug in the markdown link linter that makes it
306
+ > unable to recognize absolute paths where the absolute link starts in a parent
307
307
> folder.
308
- > For example, if having a markdown file in ` /Examples/README.md ` ,
309
- > and that file contain an absolute link pointing to ` /Examples/Resources/SqlAG ` ,
308
+ > For example, if a markdown file ` /Examples/README.md ` ,
309
+ > contains an absolute link pointing to ` /Examples/Resources/SqlAG ` ,
310
310
> that link will fail the test. Changing the link to a relative link from the
311
311
> README.md file's folder, e.g ` Resources/SqlAG ` will pass the test.
312
312
> See issue [ vors/MarkdownLinkCheck #5 ] ( https://github.com/vors/MarkdownLinkCheck/issues/5 ) .
You can’t perform that action at this time.
0 commit comments