From 66d0b77749da8250acf123fe843183e0e5a22c15 Mon Sep 17 00:00:00 2001
From: John Althouse <84981330+john-althouse@users.noreply.github.com>
Date: Mon, 30 Oct 2023 16:33:40 -0400
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index ff8da74..4700f23 100644
--- a/README.md
+++ b/README.md
@@ -86,9 +86,9 @@ Additional JA4+ methods are in the works...
 
 ## Licensing
 
-JA4: TLS Client Fingerprinting is open-source, BSD 3-Clause, same as JA3. This allows any company or tool currently utilizing JA3 to immediately upgrade to JA4 without delay.
+JA4: TLS Client Fingerprinting is open-source, BSD 3-Clause, same as JA3 and FoxIO is not planning to pursue patent coverage for JA4 TLS Client Fingerprinting. This allows any company or tool currently utilizing JA3 to immediately upgrade to JA4 without delay.
 
-JA4+, which includes JA4S, JA4L, JA4H, JA4X, JA4SSH, and all future additions, are licensed under the FoxIO License 1.1. This license is permissive for most use cases, including for academic and internal business purposes, but is not permissive for monetization. If, for example, a company would like to use JA4+ internally to help secure their own company, then that is permitted. If, for example, a vendor would like to implement JA4+ into one of their products, they would need to purchase an OEM license from us.
+JA4+, which includes JA4S, JA4L, JA4H, JA4X, JA4SSH, and all future additions, are licensed under the FoxIO License 1.1. This license is permissive for most use cases, including for academic and internal business purposes, but is not permissive for monetization. If, for example, a company would like to use JA4+ internally to help secure their own company, that is permitted. If, for example, a vendor would like to sell JA4+ fingerprinting as part of their product offering, they would need to purchase an OEM license from us.
 
 All JA4+ methods are patent pending.