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: 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 {ref}/ml-update-job.html[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
  
  