Fix links to Plugins sections (#5355)

cypress-io · Jul 5, 2023 · 8268400 · 8268400
1 parent ea0400f
commit 8268400
Show file tree

Hide file tree

Showing 6 changed files with 7 additions and 7 deletions.
diff --git a/docs/api/cypress-api/custom-commands.mdx b/docs/api/cypress-api/custom-commands.mdx
@@ -911,6 +911,6 @@ repository for a working example.
   [Writing a Custom Cypress Command](https://glebbahmutov.com/blog/writing-custom-cypress-command/)
   and
   [How to Publish Custom Cypress Command on NPM](https://glebbahmutov.com/blog/publishing-cypress-command/).
-- [Plugins using custom commands](/plugins#Custom%20Commands)
+- [Plugins using custom commands](/plugins#custom-commands)
 - [Cypress.log()](/api/cypress-api/cypress-log)
 - [Recipe: Logging In](/examples/recipes)
diff --git a/docs/api/table-of-contents.mdx b/docs/api/table-of-contents.mdx
@@ -170,7 +170,7 @@ Cypress exposes interfaces to write
 details.
 
 The Cypress community has created a large number of
-[Command Plugins](/plugins#Custom%20Commands) which you can install or download.
+[Command Plugins](/plugins#custom-commands) which you can install or download.
 
 ### APIs
 

diff --git a/docs/examples/recipes.mdx b/docs/examples/recipes.mdx
@@ -65,7 +65,7 @@ Recipes show you how to test common scenarios in Cypress.
 | [Json Web Tokens](https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/logging-in__jwt)                   | Log in using JWT                            |
 | [Using application code](https://github.com/cypress-io/cypress-example-recipes/tree/master/examples/logging-in__using-app-code) | Log in by calling the application code      |
 
-Also see [Authentication plugins](/plugins#Authentication) and watch
+Also see [Authentication plugins](/plugins#authentication) and watch
 [Organizing Tests, Logging In, Controlling State](https://www.youtube.com/watch?v=5XQOK0v_YRE)
 
 ## Preprocessors

diff --git a/docs/faq/questions/using-cypress-faq.mdx b/docs/faq/questions/using-cypress-faq.mdx
@@ -704,7 +704,7 @@ email's functionality and visual style:
 
 3. You can use a 3rd party email service that provides temporary email addresses
    for testing. Some of these services even offer a
-   [Cypress plugin](/plugins#Email) to access emails.
+   [Cypress plugin](/plugins#email) to access emails.
 
 ## <Icon name="angle-right" /> How do I wait for multiple requests to the same url?
 
@@ -914,7 +914,7 @@ You can modify the screenshot and video size when running headlessly with
 ## <Icon name="angle-right" /> Does Cypress support ES7?
 
 Yes. You can customize how specs are processed by using one of our
-[preprocessor plugins](/plugins) or by
+[preprocessor plugins](/plugins#preprocessors) or by
 [writing your own custom preprocessor](/api/plugins/preprocessors-api).
 
 Typically you'd reuse your existing Babel and webpack configurations.

diff --git a/docs/guides/core-concepts/writing-and-organizing-tests.mdx b/docs/guides/core-concepts/writing-and-organizing-tests.mdx
@@ -1029,7 +1029,7 @@ preprocessor explicitly: it exposes options that allow you to configure behavior
 such as _what_ is watched and the delay before emitting an "update" event after
 a change.
 
-Cypress also ships other [file-watching preprocessors](/plugins#Preprocessors);
+Cypress also ships other [file-watching preprocessors](/plugins#preprocessors);
 you'll have to configure these explicitly if you want to use them.
 
 - [Cypress Watch Preprocessor](https://github.com/cypress-io/cypress-watch-preprocessor)

diff --git a/docs/guides/references/best-practices.mdx b/docs/guides/references/best-practices.mdx
@@ -445,7 +445,7 @@ email's functionality and visual style:
    exposes an API to read off emails. You will then need the proper
    authentication credentials, which your server could provide, or you could use
    environment variables. Some email services already provide
-   [Cypress plugins](/plugins#Email) to access emails.
+   [Cypress plugins](/plugins#email) to access emails.
 
 ## Having Tests Rely On The State Of Previous Tests