Copilot content exclusions clarifications (#54925)

Author: mpchenette

content/copilot/managing-copilot/configuring-and-auditing-content-exclusion/excluding-content-from-github-copilot.md

@@ -50,13 +50,17 @@ Repository administrators{% ifversion ghec %}, organization owners, and enterpri
 | The {% data variables.product.github %} website |                Not applicable                 |           {% octicon "check" aria-label="Supported" %}           |
 | {% data variables.product.prodname_mobile %}    |                Not applicable                 |           {% octicon "check" aria-label="Supported" %}           |
 
+Content exclusions also apply to {% data variables.copilot.copilot_code-review_short %} on the {% data variables.product.github %} website.
+
 > [!NOTE]
 > Content exclusion is in {% data variables.release-phases.public_preview %} on the {% data variables.product.github %} website and in {% data variables.product.prodname_mobile %} and is subject to change.
 
 ### Limitations of content exclusions
 
 {% data reusables.copilot.content-exclusion-limitations %}
 
+Currently, content exclusions do not apply to symbolic links (symlinks).
+
 ### Data sent to {% data variables.product.prodname_dotcom %}
 
 After you configure content exclusion, the client (for example, the {% data variables.product.prodname_copilot_short %} extension for {% data variables.product.prodname_vscode_shortname %}) sends the current repository URL to the {% data variables.product.prodname_dotcom %} server so that the server can return the correct policy to the client. These URLs are not logged anywhere.