Update poor-performance-calling-lookup-functions.md

according to code review for LsaDbpLookupNamesBuildWorkList, the forest trust won't be used for isolated name lookup, as long as the trust has the attribute TRUST_ATTRIBUTE_FOREST_TRANSITIVE.

Author: james-msft

support/windows-server/active-directory/poor-performance-calling-lookup-functions.md

@@ -16,7 +16,7 @@ When calling the **LookupAccountName** or **LsaLookupNames** function to resolve
 
 For example, poor performance might occur when using scripts or tools (such as *Cacls.exe*, *Xcacls.exe*, *icacls.exe*, *Dsacls.exe*, and *Subinacl.exe*) to call the functions to edit security settings.
 
-The problem may show up when you have many trusted domains or forests (applies to both external and forest trusts), and/or some of these domains or forests are offline or slow to respond.
+The problem may show up when you have many trusted domains or external forest trusts, and/or some of these domains or forests are offline or slow to respond.
 
 When the functions are called for an isolated name (the format is AccountName in contrast to domain\AccountName), a remote procedure call (RPC) is made to domain controllers on all trusted domains/forests. This issue might occur if the primary domain has many trust relationships with other domains/forests or if it's doing many lookups at a same time. For example, a script is configured to run at the startup of many clients, or many trusted domains/forests use the same script simultaneously.