From a9da1b75f62b83879bcac5e4c2c3f671e2b93c8c Mon Sep 17 00:00:00 2001
From: kuqin12 <42554914+kuqin12@users.noreply.github.com>
Date: Tue, 31 Oct 2023 11:02:04 -0700
Subject: [PATCH] Update SetupDataPkg/Docs/Profiles/Overview.md

Co-authored-by: Aaron <105021049+apop5@users.noreply.github.com>
---
 SetupDataPkg/Docs/Profiles/Overview.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/SetupDataPkg/Docs/Profiles/Overview.md b/SetupDataPkg/Docs/Profiles/Overview.md
index 5f926419..f4154541 100644
--- a/SetupDataPkg/Docs/Profiles/Overview.md
+++ b/SetupDataPkg/Docs/Profiles/Overview.md
@@ -132,7 +132,8 @@ following the statements outlined in the [section above](#flow).
 Platforms also can provide a 2-character name and/or 1-byte ID for each profile. These are used to identify the profile
 by the selector, which could be BMC, OS, or other.
 
-In firmware, the name and ID are provided in the `gProfileFlavorNames` and `gProfileFlavorIds`, respectively. Platforms
+In firmware, the name and ID are auto generated and can be accessed through `gProfileFlavorNames` and `gProfileFlavorIds`, respectively. Platforms
+
 can elect to create HOBs for these meta data information and provide them to the selector. See example [here](https://github.com/microsoft/mu_oem_sample/tree/release/202302/OemPkg/OemConfigPolicyCreatorPei).
 
 To integrate the name and ID into the build, platforms can add the following to their build by following the statements: