From 7821660f8a10e79873fda361453df617277e1aba Mon Sep 17 00:00:00 2001
From: Dan Heath <76443935+Dan-Heath@users.noreply.github.com>
Date: Mon, 29 Apr 2024 22:16:36 +0000
Subject: [PATCH] backport of commit 257ff07b830dade9f02fe34f3ab1cf321b1f2062

---
 website/content/docs/api-clients/api/index.mdx | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/website/content/docs/api-clients/api/index.mdx b/website/content/docs/api-clients/api/index.mdx
index f4235a3104..7281f4f12d 100644
--- a/website/content/docs/api-clients/api/index.mdx
+++ b/website/content/docs/api-clients/api/index.mdx
@@ -92,7 +92,8 @@ Responses may contain the following headers:
 - `X-Correlation-ID` - Identifies a transaction over a series of requests and responses.
 The `X-Correlation-ID` header is a universally unique identifier (UUIDv4).
 If you provide an `X-Correlation-ID` header in an HTTP request, Boundary logs that value for all audit events related to the request.
-It uses that value as the header when it makes related requests to an external system, such as Vault, so that you can correlate the event between the product logs.
+It then uses that value as the header when it makes related requests to an external system, such as Vault, so that you can correlate the event between the product logs.
+If you do not provide an `X-Correlation-ID` header, Boundary generates a unique value for each incoming request.
 
 ## Manage system resources