anchor.diff:  // CONSOLE
   // TEST[setup:ml_filter_safe_domains]
   
  -Note that we can provide scope for any of the partition/over/by fields.
  +Note that we can use any of the `partition_field_name`, `over_field_name`, or 
  +`by_field_name` fields in the `scope`.
  +
   In the following example we scope multiple fields:
   
   [source,js]
  
positive.code: 
  ==== Specifying rule scope
  
  Let us assume we are configuring a job in order to DNS data exfiltration.
  Our data contain fields "subdomain" and "highest_registered_domain".
  We can use a detector that looks like `high_info_content(subdomain) over highest_registered_domain`.
  If we run such a job it is possible that we discover a lot of anomalies on 
  
negative.code: ----------------------------------
  // CONSOLE
  
  Now, we can create our job specifying a scope that uses the `safe_domains` 
  filter for the `highest_registered_domain` field:
  
  [source,js]
  ----------------------------------
  