Update faq.md

Co-authored-by: Máté Barabás <barabasmate@gmail.com>

Author: jtracey93

docs/content/resources/faq.md

@@ -84,7 +84,7 @@ Today, the AVM program is scoped specifically to **Azure cloud resources** and d
 
 AVM's core value is the **standardization of Azure resource configurations** via Bicep and Terraform, providing consistent interfaces for things like WAF alignment, RBAC, diagnostic settings, and private networking. We have investigated whether this standardization model can be applied to other Microsoft cloud products (for example, we have spoken to relevant product group teams on Entra ID) and, for today, we have concluded there is no meaningful impact to be had by creating standalone modules for objects such as an Entra ID group.
 
-This is not a permanent ruling. AVM is not opposed to expanding scope to cover other Microsoft cloud products. If there are valid reasons to wrap these resources inside AVM modules and a recognised standardisation surface can be defined (comparable to what AVM provides for Azure resources today), we are open to that conversation. We encourage the community to raise proposals via a [GitHub Issue](https://github.com/Azure/Azure-Verified-Modules/issues).
+This is not a permanent decision. Generally speaking, the AVM team is open to any conversation about expanding scope to cover other Microsoft cloud products. If there are valid reasons to wrap these assets inside AVM modules and a recognized standardization surface can be defined (comparable to what AVM provides for Azure resources today), we are open to that conversation. We encourage the community to raise proposals via a [GitHub Issue](https://github.com/Azure/Azure-Verified-Modules/issues).
 
 **What about pattern modules?** Resources from other Microsoft cloud products may still be included in **pattern modules** as native resource declarations, where they add meaningful value to the overall architecture pattern being described. Per the AVM specifications ([PMNFR2]({{% siteparam base %}}/spec/PMNFR2)), pattern modules may use native resource code where necessary. The restriction above applies specifically to **standalone resource modules** for these platforms.