Repository: phoenixframework/phoenix
Pull request #4184 (2021-01-27 14:15:34)

Exclude non-relevant words from links
In the same fashion of
https://github.com/phoenixframework/phoenix/pull/4175


Patch:
diff --git a/CHANGELOG.md b/CHANGELOG.md
index da4da6f1e..0f8cb7003 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -30,4 +30,4 @@ Phoenix v1.6 requires Elixir v1.9+.
 
 ## v1.5
 
-The CHANGELOG for v1.5 releases can be found [in the v1.5 branch](https://github.com/phoenixframework/phoenix/blob/v1.5/CHANGELOG.md).
+The CHANGELOG for v1.5 releases can be found in the [v1.5 branch](https://github.com/phoenixframework/phoenix/blob/v1.5/CHANGELOG.md).
diff --git a/README.md b/README.md
index 16726bdb7..a26c22e2a 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@ Phoenix.js documentation is available at [https://hexdocs.pm/phoenix/js](https:/
 
 ## Contributing
 
-We appreciate any contribution to Phoenix. Check our [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) and [CONTRIBUTING.md](CONTRIBUTING.md) guides for more information. We usually keep a list of features and bugs [in the issue tracker][4].
+We appreciate any contribution to Phoenix. Check our [CODE_OF_CONDUCT.md](CODE_OF_CONDUCT.md) and [CONTRIBUTING.md](CONTRIBUTING.md) guides for more information. We usually keep a list of features and bugs in the [issue tracker][4].
 
 ### Generating a Phoenix project from unreleased versions
 
diff --git a/guides/controllers.md b/guides/controllers.md
index 1b5abd7d6..40c5450cd 100644
--- a/guides/controllers.md
+++ b/guides/controllers.md
@@ -131,7 +131,7 @@ It is worth noting that the `text/2`, `json/2`, and `html/2` functions require n
 
 The `json/2` function is obviously useful for writing APIs, and the other two may come in handy, but most of the times we use Phoenix views to build our responses. For this, Phoenix provides the `render/3` function.
 
-Let's rollback our `show` action to what we originally wrote [in the Request life-cycle guide](request_lifecycle.html):
+Let's rollback our `show` action to what we originally wrote in the [Request life-cycle guide](request_lifecycle.html):
 
 ```elixir
 defmodule HelloWeb.HelloController do
diff --git a/guides/plug.md b/guides/plug.md
index 49bda8c2a..9a0f96918 100644
--- a/guides/plug.md
+++ b/guides/plug.md
@@ -61,7 +61,7 @@ Host: "localhost"
 Headers: [...]
 ```
 
-Our Plug simply prints information from the connection. Although our initial Plug is very simple, you can virtually do anything you want inside of it. To learn about all fields available in the connection and all of the functionality associated to it, [see the documentation for Plug.Conn](https://hexdocs.pm/plug/Plug.Conn.html).
+Our Plug simply prints information from the connection. Although our initial Plug is very simple, you can virtually do anything you want inside of it. To learn about all fields available in the connection and all of the functionality associated to it, see the [documentation for Plug.Conn](https://hexdocs.pm/plug/Plug.Conn.html).
 
 Now let's look at the other flavor plugs come in, module plugs.
 
diff --git a/guides/realtime/presence.md b/guides/realtime/presence.md
index 028faa582..9f20d1f14 100644
--- a/guides/realtime/presence.md
+++ b/guides/realtime/presence.md
@@ -44,7 +44,7 @@ children = [
 ]
 ```
 
-Next we will create a channel that Presence can communicate on. For this example we will create a `RoomChannel` ([see the channels guide for more details on this](channels.html)):
+Next we will create a channel that Presence can communicate on. For this example we will create a `RoomChannel` (see the [channels guide](channels.html) for more details on this):
 
 ```console
 $ mix phx.gen.channel Room
diff --git a/guides/routing.md b/guides/routing.md
index ca36abedc..6592c9c16 100644
--- a/guides/routing.md
+++ b/guides/routing.md
@@ -693,7 +693,7 @@ forward "/jobs", BackgroundJob.Plug, name: "Hello Phoenix"
 
 There is a fourth `router_opts` argument that can be passed. These options are outlined in the `Phoenix.Router.scope/2` documentation.
 
-`BackgroundJob.Plug` can be implemented as any module plug discussed in the [Plug guide](plug.html). Note though it is not advised to forward to another Phoenix endpoint. This is because plugs defined by your app and the forwarded endpoint would be invoked twice, which may lead to errors.
+`BackgroundJob.Plug` can be implemented as any Module Plug discussed in the [Plug guide](plug.html). Note though it is not advised to forward to another Phoenix endpoint. This is because plugs defined by your app and the forwarded endpoint would be invoked twice, which may lead to errors.
 
 ## Summary
 


Test patch:
diff --git a/guides/testing/testing_channels.md b/guides/testing/testing_channels.md
index 39b3fbedc..2fe4b477b 100644
--- a/guides/testing/testing_channels.md
+++ b/guides/testing/testing_channels.md
@@ -57,7 +57,7 @@ defmodule HelloWeb.ChannelCase do
 end
 ```
 
-It is very straight-forward. It sets up a case template that imports all of `Phoenix.ChannelTest` on use. In the `setup` block, it starts the SQL Sandbox, which we discussed [in the Testing Contexts guide](testing_contexts.html).
+It is very straight-forward. It sets up a case template that imports all of `Phoenix.ChannelTest` on use. In the `setup` block, it starts the SQL Sandbox, which we discussed in the [Testing contexts guide](testing_contexts.html).
 
 ## Subscribe and joining
 
diff --git a/guides/testing/testing_controllers.md b/guides/testing/testing_controllers.md
index 44f692fc0..b2c6d965d 100644
--- a/guides/testing/testing_controllers.md
+++ b/guides/testing/testing_controllers.md
@@ -278,7 +278,7 @@ defmodule HelloWeb.ArticleView do
 end
 ```
 
-We talked about `render_many` [in the Views and Templates guide](views.html). All we need to know for now is that all JSON replies have a "data" key with either a list of posts (for index) or a single post inside of it.
+We talked about `render_many` in the [Views and templates guide](views.html). All we need to know for now is that all JSON replies have a "data" key with either a list of posts (for index) or a single post inside of it.
 
 Let's take a look at the test for the `index` action then:
 
@@ -382,7 +382,7 @@ end
 
 It simply posts to the `create` path with invalid parameters. This makes it return a JSON response, with status code 422, and a response with a non-empty "errors" key.
 
-The `action_fallback` can be extremely useful to reduce boilerplate when designing APIs. You can learn more about the "Action Fallback" [in the Controllers guide](controllers.html).
+The `action_fallback` can be extremely useful to reduce boilerplate when designing APIs. You can learn more about the "Action Fallback" in the [Controllers guide](controllers.html).
 
 ### The `delete` action