Merge pull request #743 from codacy/doc/open-links-same-window-DOCS-145

doc: Always open links on the same window DOCS-145

Author: Paulo Ribeiro

docs/configuration/integrations/bitbucket-server.md

@@ -27,7 +27,7 @@ To integrate Codacy with Bitbucket Server, you must create an application link o
     !!! important
         **If you're using Bitbucket Server 7.20 or later** you must select the application type **Atlassian product** while creating the new application link.
 
-        This [forces the integration to use OAuth 1.0](https://confluence.atlassian.com/bitbucketserver/link-to-other-applications-1018764620.html#Linktootherapplications-LinktoAtlassianproductsorexternalapplicationsusingOAuth1.0){: target="_blank"} and is necessary to ensure the compatibility between Codacy and older versions of Bitbucket that only supported OAuth 1.0.
+        This [forces the integration to use OAuth 1.0](https://confluence.atlassian.com/bitbucketserver/link-to-other-applications-1018764620.html#Linktootherapplications-LinktoAtlassianproductsorexternalapplicationsusingOAuth1.0) and is necessary to ensure the compatibility between Codacy and older versions of Bitbucket that only supported OAuth 1.0.
 
     ![Bitbucket Server application link](images/bitbucket-server-application-link.png)
 

docs/configuration/integrations/github-app-create.md

@@ -15,7 +15,7 @@ To create the GitHub App:
     | GitHub App name                         | Codacy                                                  |
     | Homepage URL                            | `https://codacy.example.com`                            |
     | User authorization callback URL         | `https://codacy.example.com`                            |
-    | Expire user authorization tokens        | Disabled<br/><br/><strong>⚠️ Note:</strong> Currently, Codacy doesn't support <a href="https://docs.github.com/en/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens" target="_blank">expiring user access tokens</a>. Make sure that this option is turned off. |
+    | Expire user authorization tokens        | Disabled<br/><br/><strong>⚠️ Note:</strong> Currently, Codacy doesn't support <a href="https://docs.github.com/en/developers/apps/building-github-apps/refreshing-user-to-server-access-tokens">expiring user access tokens</a>. Make sure that this option is turned off. |
     | Webhook URL                             | For GitHub Cloud:<br/>`https://codacy.example.com/2.0/events/gh/organization`<br/><br/>For GitHub Enterprise:<br/>`https://codacy.example.com/2.0/events/ghe/organization` |
     | **Repository permissions**              |                                                         |
     | Administration                          | Read & write                                            |

docs/configuration/logging.md

@@ -66,7 +66,7 @@ Follow these instructions to configure the log level:
 
 ## Configuring the log retention period
 
-The log retention period is the number of days during which logs will be stored before being removed by the [MinIO bucket lifecycle configuration policy](https://docs.min.io/docs/minio-bucket-lifecycle-guide.html){: target="_blank"} that we provide in the template [lifecycle-police-job.yaml](https://github.com/codacy/chart/blob/master/codacy/templates/fluentd/lifecycle-police-job.yaml).
+The log retention period is the number of days during which logs will be stored before being removed by the [MinIO bucket lifecycle configuration policy](https://docs.min.io/docs/minio-bucket-lifecycle-guide.html) that we provide in the template [lifecycle-police-job.yaml](https://github.com/codacy/chart/blob/master/codacy/templates/fluentd/lifecycle-police-job.yaml).
 
 Follow these instructions to configure the log retention period:
 

docs/index.md

@@ -68,7 +68,7 @@ Install Codacy on an existing cluster using our Helm chart:
         --namespace codacy
     ```
 
-4.  Download the template file [`values-production.yaml`](./values-files/values-production.yaml){: target="_blank"} and use a text editor of your choice to edit the value placeholders as described in the comments.
+4.  Download the template file [`values-production.yaml`](./values-files/values-production.yaml) and use a text editor of your choice to edit the value placeholders as described in the comments.
 
 5.  Create an address record on your DNS provider mapping the hostname you used in the previous step to the IP address of your Ingress controller.