update as per a review

Author: jaehyeon-kim

README.md

@@ -572,9 +572,9 @@ Core services like Flink, Spark, and Kafka Connect are designed to be modular an
 
 ### Update Kpow and Flex Licenses
 
-Both **Kpow** and **Flex** require valid licenses. All licenses are now managed through our unified portal. Visit [https://account.factorhouse.io/auth/getting_started](https://account.factorhouse.io/auth/getting_started) to generate your license.
+Both **Kpow** and **Flex** require valid licenses. Licenses can be obtained from the Factor House License Portal. Visit [https://account.factorhouse.io/auth/getting_started](https://account.factorhouse.io/auth/getting_started) to generate your license.
 
-You can begin with either option:
+You can begin with either of the following options:
 
 - Request a free **Community License** for non-commercial use. A single community license now covers both Kpow and Flex.
 - Request a **30-day Trial License** for commercial evaluation, providing full access to all enterprise features.
@@ -583,7 +583,7 @@ For managing Kpow and Flex licenses effectively, it's strongly recommended to st
 
 The Docker Compose files facilitates this by allowing you to specify the path to your license file using **environment variables** on your host machine _before_ launching the services. Specifically, they are configured to look for these variables and use their values to locate the appropriate license file via the `env_file` directive. If an environment variable is not set, a default path (usually within the `resources` directory) is used as a fallback.
 
-Regardless of the edition, Kpow and Flex expect a single license file. While the community edition utilizes a single license, separate environment variables are maintained for consistency with enterprise license configurations.
+Factor House Community licenses can be used across both Flex and Kpow, however individual trial licenses are required for evaluation. To enforce consistency, Kpow and Flex both require the license variable to be set on a product-by-product basis, regardless of which license you're using (this also applies to enterprise license configurations).
 
 Therefore, you should specify the path to your license file for both environment variables: