Update traffic-identification.md

whiskeykilo · web-flow · commit e0dccb66df1a · 2021-08-12T12:55:00.000-04:00
diff --git a/docs/programs/traffic-identification.md b/docs/programs/traffic-identification.md
@@ -7,7 +7,7 @@ id: "programs/traffic-identification"
 There are several ways to identify hacker testing traffic at various layers for testing/feature enablement or testing control & monitoring.
 
 ### Application Layer: User Allowlisting
-* HackerOne provides each hacker with a forwarding email [address](https://docs.hackerone.com/hackers/hacker-email-alias.html)
+* HackerOne provides each hacker with a forwarding [email address](https://docs.hackerone.com/hackers/hacker-email-alias.html)
     * This email can be helpful in identifying hacker testing accounts for allowlisting within the application itself
 ### Session Layer: HTTP Headers
 * Researchers may add headers to requests such as: “X-HackerOne-Research: [H1 username]”
@@ -21,4 +21,4 @@ There are several ways to identify hacker testing traffic at various layers for
 * HackerOne [Clear](https://docs.hackerone.com/programs/hackerone-clear.html) researchers
 * Custom alert process for each program
     * email, phone, [Slack, Teams, PagerDuty, and others](https://docs.hackerone.com/programs/supported-integrations.html)
-    * HackerOne [API](https://api.hackerone.com)
+    * HackerOne [API](https://api.hackerone.com)
