diff --git a/docs/content/connectors/upstream/toolreference.md b/docs/content/connectors/upstream/toolreference.md index 04810f4970..530366ba58 100644 --- a/docs/content/connectors/upstream/toolreference.md +++ b/docs/content/connectors/upstream/toolreference.md @@ -2118,7 +2118,7 @@ Enter `https://semgrep.dev/api/v1/` in the **Location** field. 1. Enter a valid API key in the **Secret** field. You can find this on the Tokens page: ​ -"Settings" in the left navbar \> Tokens \> Create new token ([https://semgrep.dev/orgs/\-/settings/tokens389) +"Settings" in the left navbar \> Tokens \> Create new token ([https://semgrep.dev/orgs/\-/settings/tokens](https://semgrep.dev/orgs/-/settings/tokens)) See [Semgrep documentation](https://semgrep.dev/docs/semgrep-cloud-platform/semgrep-api/#tag__badge-list) for more info. @@ -2178,7 +2178,7 @@ The Snyk connector uses the Snyk REST API to fetch data. #### Connector Mappings -1. Enter **[https://api.snyk.io/rest394** or **[https://api.eu.snyk.io/rest395** (for a regional EU deployment) in the **Location** field. +1. Enter **[https://api.snyk.io/rest](https://api.snyk.io/v1)** or **[https://api.eu.snyk.io/rest](https://api.eu.snyk.io/v1)** (for a regional EU deployment) in the **Location** field. 2. Enter a valid API key in the **Secret** field. API Tokens are found on a user's **[Account Settings](https://docs.snyk.io/getting-started/how-to-obtain-and-authenticate-with-your-snyk-api-token)** [page](https://docs.snyk.io/getting-started/how-to-obtain-and-authenticate-with-your-snyk-api-token) in Snyk. See the [Snyk API documentation](https://docs.snyk.io/snyk-api) for more info. diff --git a/docs/content/get_started/about/about_defectdojo.md b/docs/content/get_started/about/about_defectdojo.md index efad1ef35b..5e27faa64f 100644 Binary files a/docs/content/get_started/about/about_defectdojo.md and b/docs/content/get_started/about/about_defectdojo.md differ diff --git a/docs/content/get_started/contributing/documentation.md b/docs/content/get_started/contributing/documentation.md index 445308ca90..90d6463755 100644 Binary files a/docs/content/get_started/contributing/documentation.md and b/docs/content/get_started/contributing/documentation.md differ diff --git a/docs/content/get_started/contributing/how-to-write-a-parser.md b/docs/content/get_started/contributing/how-to-write-a-parser.md index e3cbf97281..6ed8c1e8e4 100644 --- a/docs/content/get_started/contributing/how-to-write-a-parser.md +++ b/docs/content/get_started/contributing/how-to-write-a-parser.md @@ -385,4 +385,4 @@ Please add a new .md file in [`docs/content/en/connecting_your_tools/parsers`] w * A link to the relevant unit tests folder so that users can quickly navigate there from Documentation. * A link to the scanner itself - (e.g. GitHub or vendor link) -Here is an example of a completed Parser documentation page: [https://github.com/DefectDojo/django-DefectDojo/blob/master/docs/content/supported_tools/file/acunetix.md77 +Here is an example of a completed Parser documentation page: [https://github.com/DefectDojo/django-DefectDojo/blob/master/docs/content/supported_tools/file/acunetix.md](https://github.com/DefectDojo/django-DefectDojo/blob/master/docs/content/supported_tools/file/acunetix.md) diff --git a/docs/content/issue_tracking/pro_integration/messaging_connectors.md b/docs/content/issue_tracking/pro_integration/messaging_connectors.md index 74ad33a2ec..d7a594d1a3 100644 Binary files a/docs/content/issue_tracking/pro_integration/messaging_connectors.md and b/docs/content/issue_tracking/pro_integration/messaging_connectors.md differ