Merge pull request testing-library#203 from kachkaev/fix-links-to-guiding-principles

afontcu · web-flow · commit 4ddc656d8bad · 2019-08-01T13:22:47.000+02:00
Fix links to guiding-principles.md
diff --git a/docs/dom-testing-library/api-queries.md b/docs/dom-testing-library/api-queries.md
@@ -626,7 +626,7 @@ cy.getByTestId('username-input').should('exist')
 
 <!--END_DOCUSAURUS_CODE_TABS-->
 
-> In the spirit of [the guiding principles](#guiding-principles), it is
+> In the spirit of [the guiding principles](guiding-principles.md), it is
 > recommended to use this only after the other queries don't work for your use
 > case. Using data-testid attributes do not resemble how your software is used
 > and should be avoided if possible. That said, they are _way_ better than
diff --git a/docs/marko-testing-library/intro.md b/docs/marko-testing-library/intro.md
@@ -35,7 +35,7 @@ components. It provides light utility functions on top of
 in a way that encourages better testing practices. Its primary guiding principle
 is:
 
-> [The more your tests resemble the way your software is used, the more confidence they can give you.](#guiding-principles)
+> [The more your tests resemble the way your software is used, the more confidence they can give you.](guiding-principles.md)
 
 So rather than dealing with instances of rendered Marko components, your tests
 will work with actual DOM nodes. The utilities this library provides facilitate
diff --git a/docs/vue-testing-library/intro.md b/docs/vue-testing-library/intro.md
@@ -14,7 +14,7 @@ In short, Vue Testing Library does three things:
 
 1. Re-exports query utilities and helpers from `DOM Testing Library`.
 2. Hides `@vue/test-utils` methods that are in conflict with Testing Library
-   [Guiding Principle](/docs/guiding-principles).
+   [Guiding Principle](guiding-principles.md).
 3. Tweaks some methods from both sources.
 
 ## Quickstart
