add osquery notes for 7.16

docs/osquery/osquery.asciidoc

@@ -287,14 +287,22 @@ you can create roles for users who can only run live or saved queries, but who c
 This is useful for teams who need in-depth and detailed control.
 
 [float]
-=== Customize Osquery configuration
+=== experimental[] Customize Osquery configuration
 By default, all Osquery Manager integrations share the same osquery configuration. However, you can customize how Osquery is configured by editing the Osquery Manager integration for each agent policy
 you want to adjust. The custom configuration is then applied to all agents in the policy. 
 This powerful feature allows you to configure
 https://osquery.readthedocs.io/en/stable/deployment/file-integrity-monitoring[File Integrity Monitoring], https://osquery.readthedocs.io/en/stable/deployment/process-auditing[Process auditing], 
 and https://osquery.readthedocs.io/en/stable/deployment/configuration/#configuration-specification[others].
 
-IMPORTANT: Take caution when editing this configuration. The changes you make are distributed to all agents in the policy.
+[IMPORTANT]
+=========================
+
+* Take caution when editing this configuration. The changes you make are distributed to all agents in the policy.
+
+* Do not edit any `packs` configuration using this field. 
+When you add a pack from the Osquery *Packs* page in {kib}, this adds the definition to the *Osquery config* JSON field. 
+However, once a pack is added, it should only be edited from the Osquery *Packs* page.
+=========================
 
 . From the {kib} main menu, click *Fleet*, then the *Agent policies* tab.
 
@@ -316,6 +324,16 @@ IMPORTANT: Take caution when editing this configuration. The changes you make ar
 
 . Click *Save integration* to apply the custom configuration to all agents in the policy.
 
+As an example, the following configuration disables two tables.
+
+```
+{
+   "options":{
+      "disable_tables":"curl,process_envs"
+   }
+}
+```
+
 [float]
 === Upgrade Osquery versions