update advanced scrubbing doc - adding logs section

docs/security-legal-pii/scrubbing/advanced-datascrubbing.mdx

@@ -233,3 +233,21 @@ The following limitations generally apply to all server-side data scrubbing, be
 - Sentry's internals require that the event user's IP address must either be `null` or a valid IPv4/IPv6 address. If you're trying to hash, mask or replace IP addresses, data scrubbing will move the replacement value into the user ID (if one is not already set) in order to avoid breaking this requirement while still providing useful data for the Users count on an issue.
 
 - In stack traces, scrubbing works on file paths but not on a file's base name. This would violate assumptions in the processing pipeline resulting in a poor user experience. Instead, you can scrub a file's base name in the SDK itself, using the [`RewriteFrames` integration](https://docs.sentry.io/platforms/javascript/configuration/integrations/rewriteframes/) or [`beforeSend`](https://docs.sentry.io/platforms/javascript/configuration/filtering/).
+
+## Data Scrubbing for Logs
+
+[Logs](/product/explore/logs/) will honor the default [Server-Side Data Scrubbing rules](/security-legal-pii/scrubbing/server-side-scrubbing/#geographic-information)  applied to your projects. To add advanced data scrubbing rules for Logs, start by choosing the dataset.
+
+![Add an advanced data scrubbing rule dialog showing dataset selection, method, data type, and source fields](img/data_scrub_rule.png)
+
+<Alert>
+Deep wild cards ('**') or $string / $number value selectors will apply across all datasets. For specific data types you can select the log attribute that needs to be scrubbed.
+</Alert>
+
+![Attribute field with auto-completion dropdown showing available log attributes](img/scrub_attribute.png)
+
+You can also edit existing scrubbing rules
+
+![Edit dialog showing an existing rule with custom placeholder and attribute configuration](img/scrub_edit.png)
+
+