anchor.diff:  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 with our safe domains. Those lists are called 
  -`filters` in {ml}. Filters can be shared across jobs.
  +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]:
   
  
positive.code: Let us imagine that we have configured a job and it has been running
  for some time. After observing its results we decide that we can employ
  rules in order to get rid of some uninteresting results. We can use
  the update-job API to do so. However, the rule we added will only be in effect
  for any results created from the moment we added the rule onwards. Past results
  will remain unaffected.
  
  ==== Using rules VS filtering data
  
  
negative.code: // CONSOLE
  // TEST[setup:ml_filter_safe_domains]
  
  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]
  