anchor.diff:  
   === Bad Customer
   
  -Let's assume this is a bad customer, that will not update his credit card:
  -
  -* Day 14: the customer moves to a `BLOCKED` state; the system will stop invoicing, and will indicate that the customer is not entititled to receiving service any longer (more details below)
  +Let's assume this is a bad customer, who will not update his credit card:
  +
  +* Day 14: the customer moves into a `BLOCKED` state; the system will stop invoicing, and will indicate that the customer is not entititled to receiving service any longer (more details below)
   * Day 21: the system will cancel the subscription (final state)
   
   === Good Customer
   
  -Let's assume this is a good customer, and after the WARNING, he updates his credit card:
  +Let's assume he is a good customer, and after the WARNING, he updates his credit card:
   
   * Day 15: customer updates credit card and pays his unpaid invoice(s) (more details below). The system brings back the overdue status to `CLEAR`.
  -
   
   [[platform_use]]
   == Use of the Platform
  
positive.code: 
  The overdue configuration will define the three states the account will go through:
  
  1. The account will enter the WARNING state 10 days after the first unpaid invoice
  2. 4 days later, the account will move to the BLOCKED state
  3. 7 days later, the account will move to the CANCELLATION state
  
  
negative.code: 
  [source,json]
  ---
  {
    "blockChanges": true,
    "clearState": false,
    "daysBetweenPaymentRetries": 1,
    "disableEntitlementAndChangesBlocked": false,
    "externalMessage": "Reached WARNING",
    "name": "WARNING",
    "reevaluationIntervalDays": 4
  }
  ---
  
  If the `disableEntitlementAndChangesBlocked` is set to true, it means that the customer is not entitled to the service associated to any subscriptions.
  