From 47fb7d53074dbb0d8ffe840a25383d212871ffff Mon Sep 17 00:00:00 2001
From: Surayya Huseyn Zada <114938397+surayya-MS@users.noreply.github.com>
Date: Mon, 8 Jul 2024 17:14:33 +0200
Subject: [PATCH] [BuildCheck] Fix docs (#10334)

* remove the part where we state that we can analyze binlogs of older  versions of MSBuild

* Update BuildCheck-Architecture.md
---
 documentation/specs/proposed/BuildCheck-Architecture.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/specs/proposed/BuildCheck-Architecture.md b/documentation/specs/proposed/BuildCheck-Architecture.md
index 56579dc87a..367db012bc 100644
--- a/documentation/specs/proposed/BuildCheck-Architecture.md
+++ b/documentation/specs/proposed/BuildCheck-Architecture.md
@@ -35,7 +35,7 @@ One example of rich data that might be helpful for internal analyses is [`Projec
 
 ## Execution Modes
 
-**Replay Mode** - so that users can choose to perform analyses post build, without impacting the performance of the build. And so that some level of analysis can be run on artifacts from builds produced by older versions of MSBuild.
+**Replay Mode** - so that users can choose to perform analyses post build, without impacting the performance of the build. And so that some level of analysis can be run on artifacts from builds produced by MSBuild from NET 9.0 / VS 17.12 or newer. The older versions won't be supported.
 
 **Live mode** - this is what users are used to from compilation analyses. Integrating into build execution will as well help driving adoption by opting-in users by default to some level of checking and hence exposing them to the feature.