fix new appsec go setup links

content/en/security/application_security/setup/gateway-api.md

@@ -1,8 +1,5 @@
 ---
 title: Enabling AAP for Gateway API in Kubernetes
-code_lang: gateway-api
-type: multi-code-lang
-code_lang_weight: 50
 aliases:
   - /security/application_security/threats/setup/threat_detection/gateway_api
   - /security/application_security/threats_detection/gateway_api
@@ -148,7 +145,7 @@ spec:
 
 ## Datadog Go Tracer and Gateway API integration
 
-<div class="alert alert-warning">
+<div class="alert alert-info">
   <strong>Note:</strong> The AAP Gateway API integration is built on top of the Datadog Go Tracer. It follows the same release process as the tracer, and its Docker images are tagged with the corresponding tracer version.
 </div>
 

content/en/security/application_security/setup/go/_index.md

@@ -1,10 +1,5 @@
 ---
 title: Enabling App and API Protection for Go
-aliases:
-  - /security_platform/application_security/getting_started/go
-  - /security/application_security/getting_started/go
-  - /security/application_security/threats/setup/threat_detection/go
-  - /security/application_security/threats_detection/go
 further_reading:
 - link: "/security/application_security/add-user-info/"
   tag: "Documentation"

content/en/security/application_security/setup/go/dockerfile.md

@@ -1,8 +1,5 @@
 ---
 title: Building your Go application for App and API Protection
-code_lang: docker
-type: multi-code-lang
-code_lang_weight: 10
 further_reading:
 - link: "/security/application_security/how-it-works/"
   tag: "Documentation"
@@ -15,8 +12,6 @@ further_reading:
   text: "Troubleshooting App and API Protection"
 ---
 
-# Introduction
-
 App and API Protection for Go installation requirements can be abstract and the Go toolchain
 cross-compilation and CGO capabilities can make precise installation steps difficult to understand.
 
@@ -66,7 +61,7 @@ Two main dimensions impact your Dockerfile choice for App and API Protection:
 * **libc implementation**: glibc (Debian/Ubuntu) or musl (Alpine)
 * **CGO**: enabled or disabled (with the env var `CGO_ENABLED`).
 
-These dimensions affect both build requirements and runtime compatibility. The Datadog WAF requires specific shared libraries (`libc.so.6` and `libpthread.so.0`) at runtime and the build approach varies depending on these choices. Those dependencies are required by all programs built with CGO enabled, so the Datadog WAF will work out-of-the-box on runtime environments that support such programs. 
+These dimensions affect both build requirements and runtime compatibility. The Datadog WAF requires specific shared libraries (`libc.so.6`, `libpthread.so.0` and `libdl.so.2`) at runtime and the build approach varies depending on these choices. Those dependencies are required by all programs built with CGO enabled, so the Datadog WAF will work out-of-the-box on runtime environments that support such programs. 
 
 When CGO is disabled, however, Go usually produces a fully, statically linked binary that does not require these libraries. but this is not true when using the Datadog WAF. This is why, when CGO is disabled, the `-tags=appsec` flag needs to be passed to enable the Datadog WAF.
 

content/en/security/application_security/setup/go/setup.md

@@ -1,5 +1,5 @@
 ---
-title: Enabling App and API Protection for Go
+title: Getting started for App and API Protection for Go
 aliases:
   - /security_platform/application_security/getting_started/go
   - /security/application_security/getting_started/go
@@ -26,16 +26,14 @@ further_reading:
   text: "Troubleshooting App and API Protection"
 ---
 
-## Enabling App and API Protection
+## Prerequisite
 
-### Prerequisite
-
-- The [Datadog Agent][101] is installed and configured for your application's operating system or container, cloud, or virtual environment. 
+- The [Datadog Agent][16] is installed and configured for your application's operating system or container, cloud, or virtual environment. 
 - Your service framework and tools are [compatible][2] with Datadog [Application and API Protection][1].
 - Your deployment environment is [supported][5].
 - You have one of the latest two versions of [Go][4] installed (following the [Official Release Policy][5]).
 
-### Get started
+## Get started
 
 1. Install [Orchestrion][10]:
    ```console
@@ -149,7 +147,7 @@ If you are building your Go application without [CGO][9], you can still enable A
    $ CGO_ENABLED=0 orchestrion go build -tags appsec my-program
    ```
 
-  <div class="alert alert-info">Using `CGO_ENABLED=0` usually guarantees a statically-linked binary. This is will not be the case here.</div>
+  <div class="alert alert-warning">Disabling CGO usually guarantees a statically-linked binary. This is will not be the case here.</div>
 
 2. Install `libc.so.6`, `libpthread.so.0` and `libdl.so.2` on your system, as these libraries are required by the Datadog WAF:
    This installation can be done by installing the `glibc` package on your system with your package manager. See [Creating a Dockerfile for App and API Protection for Go][3].
@@ -191,6 +189,7 @@ For more details, see [Standalone App and API Protection][8].
 
 [1]: /security/application_security/setup/compatibility/go/?tab=v2#web-framework-compatibility
 [2]: /security/application_security/setup/compatibility/go/
+[3]: /security/application_security/setup/go/dockerfile
 [4]: https://go.dev/
 [5]: https://go.dev/doc/devel/release#policy
 [6]: /security/application_security/setup/go#building-without-cgo
@@ -203,3 +202,4 @@ For more details, see [Standalone App and API Protection][8].
 [13]: https://github.com/ebitengine/purego
 [14]: https://app.datadoghq.com/security/appsec
 [15]: /security/default_rules/security-scan-detected/
+[16]: https://app.datadoghq.com/account/settings#agent