Merge docs changes around script exection and YARA (#25204)

This PR cherry-picks a couple of docs changes I added to the docs-4.63.0
branch. These changes were approved and merged in
#25181 and
#25189, before I belatedly asked
whether that was the correct process.

docs/Configuration/agent-configuration.md

@@ -497,7 +497,7 @@ How to update agent options:
 
 The agents may take several seconds to update because Fleet has to wait for the hosts to check in. Additionally, hosts enrolled with removed enroll secrets must properly rotate their secret to have the new changes take effect.
 
-
+> When configuring a value for [`script_execution_timeout`](https://fleetdm.com/docs/configuration/agent-configuration#script-execution-timeout) in the UI, make sure to put the key at the top level of the YAML, _not_ as a child of `config`.  
 
 <meta name="pageOrderInSection" value="300">
 <meta name="description" value="Learn how to use configuration files and the fleetctl command line tool to configure agent options.">

handbook/company/pricing-features-table.yml

@@ -929,8 +929,8 @@
 #  ╩ ╩╩ ╩╩═╝╚╩╝╩ ╩╩╚═╚═╝  ═╩╝╚═╝ ╩ ╚═╝╚═╝ ╩ ╩╚═╝╝╚╝  └─ ╩ ╩ ╩╩╚═╩ ╩─┘
 - industryName: Malware detection (YARA/custom IoCs)  # TODO: consider: technically more than YARA, consider generalizing this and including the concept of comparing known binary hashes and other IoCs (either via live query or in the data lake to compare threat intel feed)
   friendlyName: Scan files for zero days and malware signatures
-  description: Use YARA signatures to report and trigger automations when zero days, malware, or unexpected files are detected on a host.
-  documentationUrl: https://fleetdm.com/tables/yara
+  description: Deploy YARA signatures (rules) to report and trigger automations when zero days, malware, or unexpected files are detected on a host.  YARA rules can be deployed remotely and privately.
+  documentationUrl: https://fleetdm.com/guides/remote-yara-rules
   tier: Free
   jamfProHasFeature: no
   jamfProtectHasFeature: yes