Skip to content

Conversation

eliottness
Copy link
Contributor

@eliottness eliottness commented Jul 29, 2025

What does this PR do? What is the motivation?

  • Add more links between pages
  • Copy paste shortcodes that are deprecated and customize them
  • Remove all references to the AAP acronym

Merge instructions

Merge readiness:

  • Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

Additional notes

Signed-off-by: Eliott Bouhana <eliott.bouhana@datadoghq.com>
@eliottness eliottness requested a review from a team as a code owner July 29, 2025 08:53
Copy link
Contributor

github-actions bot commented Jul 29, 2025

✅ Documentation Team Review

The documentation team has approved this pull request. Thank you for your contribution!

Copy link
Contributor

@michaelcretzman michaelcretzman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just making "App and API Protection" consistent.
I'm not sure we're going to get rid of AAP but for now let's use App and API Protection and not App & API Protection. Some search engines might interpret the ampersand as a separator or symbol, which could affect keyword relevancy in certain cases.

@@ -87,10 +86,12 @@ Add the following environment variable value to your application container's Doc
ENV DD_APPSEC_ENABLED=true
```

For more information on how to create a fitting docker image, See [Creating a Dockerfile for App & API Protection for Go][3].
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
For more information on how to create a fitting docker image, See [Creating a Dockerfile for App & API Protection for Go][3].
For more information on how to create a fitting docker image, See [Creating a Dockerfile for App and API Protection for Go][3].

Copy link
Contributor Author

eliottness commented Jul 30, 2025

Merge activity

  • Jul 30, 4:29 PM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Jul 30, 4:31 PM UTC: @eliottness merged this pull request with Graphite.

@eliottness eliottness merged commit a412c6d into master Jul 30, 2025
17 of 18 checks passed
@eliottness eliottness deleted the eliottness/fix-new-go-setup branch July 30, 2025 16:31
petems pushed a commit that referenced this pull request Aug 1, 2025
<!-- *Note: Please remember to review the Datadog Documentation [Contribution Guidelines](https://github.com/DataDog/documentation/blob/master/CONTRIBUTING.md) if you have not yet done so.* -->

### What does this PR do? What is the motivation?

*  Add more links between pages
* Copy paste shortcodes that are deprecated and customize them
* Remove all references to the AAP acronym

### Merge instructions

<!-- 
If you're waiting for a release or there are other considerations that you want us to be aware of, list them here. 
If the PR is ready to be merged once it receives the required reviews, check the box below after you've created the PR.
-->

Merge readiness:
- [x] Ready for merge

**For Datadog employees**:

Your branch name MUST follow the `<name>/<description>` convention and include the forward slash (`/`). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the **Squash and Merge** button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

### Additional notes
<!-- Anything else we should know when reviewing?-->

<!-- Previewing the PR: Assuming you are a Datadog employee and named your branch `<yourname>/<description>`, a preview build will run and links to the preview output will be auto-generated and posted in the PR comments. The links will 404 until the preview build is finished running. -->
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants