anchor.diff:  ----------------------------------
   // CONSOLE
   
  -Now, we can create our job specifying a scope that uses the filter for the 
  -`highest_registered_domain` field:
  +Now, we can create our job specifying a scope that uses the `safe_domains` 
  +filter for the `highest_registered_domain` field:
   
   [source,js]
   ----------------------------------
  
positive.code: // CONSOLE
  // TEST[setup:ml_filter_safe_domains]
  
  Note that we can provide scope for any of the partition/over/by fields.
  In the following example we scope multiple fields:
  
  [source,js]
  
negative.code: skip results for domains that we consider safe. Using a rule with a scope allows 
  us to achieve this.
  
  First, we need to create a list of our safe domains. Those lists are called 
  _filters_ in {ml}. Filters can be shared across jobs.
  
  We create our filter using the {ref}/ml-put-filter.html[put filter API]:
  
  