From 250ab6dd966df9b9be553581baa10d8cce1d00b1 Mon Sep 17 00:00:00 2001
From: Scott Offen <3513626+scottoffen@users.noreply.github.com>
Date: Fri, 21 Nov 2025 16:34:24 -0700
Subject: [PATCH] Update docs

---
 docs/docs/index.md | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/docs/docs/index.md b/docs/docs/index.md
index ecbadde..64d0f51 100644
--- a/docs/docs/index.md
+++ b/docs/docs/index.md
@@ -22,6 +22,18 @@ FluentHttpClient is optimized for .NET 10 and the newest .NET releases, while al
 | **.NET 9**                | ✔️        |                               |
 | **.NET 10**               | ✔️        | LTS                           |
 
+### .NETStandard Consumers
+
+Projects targeting **.NETStandard 2.0** or **.NETStandard 2.1** do not include `System.Text.Json` in the framework. FluentHttpClient uses `System.Text.Json` internally for its JSON extensions, but the package is not referenced transitively.
+
+If you are building against **netstandard2.0** or **netstandard2.1**, or any TFM that does **not** ship `System.Text.Json`, you will need to add an explicit package reference with a minimum version of 6.0.10 (a higher version is always recommended):
+
+```xml
+<PackageReference Include="System.Text.Json" Version="6.0.10" />
+```
+
+Apps targeting modern TFMs (such as .NET 5 and later) already include `System.Text.Json` and do not require this step.
+
 ## A Better Way to Send HTTP Requests
 
 FluentHttpClient is built around the way you actually write HTTP code: configure the request, send it, and handle/deserialize the response. Instead of scattering headers, query parameters, content, and deserialization across multiple calls and helper classes, you express the whole flow as a single, readable chain that sits naturally on top of `HttpClient`.