README.md in chord-0.0.6 vs README.md in chord-0.0.7

@@ -12,14 +12,10 @@
     u.attributes                              # see all attributes (returns hash)
     u.update(name: 'Joe Smith', notes: 'Etc') # update attributes
     u.add_role(3)                             # add role (by ID) to the user
     u.remove_role(3)                          # remove role (by ID) from the user
     u.subscriptions                           # fetch the user's subscriptions
-    u.update(metadata: {legacy_id: 415})      # when updating 'metadata' attribute, the given
-                                              # hash is merged into the existing value and
-                                              # keys and values are stringified (since
-                                              # metadata is stored in OMS as a JSON string)
 
     o = Chord::Order.find(1)                  # fetch order
     o.subscription_installment?               # was the order a subscription installment?
     o.subscription_start?                     # did the order start a subscription?
 
@@ -75,5 +71,9 @@
 
 Both config-loading methods return a boolean indicating whether configuration data was found and loaded, so you can easily fall back from one method to the other, for example:
 
     Chord.config_from_env or Chord.config_from_file('chord_config.yml')
 
+
+# To Do
+
+* tests should use mocks instead of real API requests