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

@@ -6,24 +6,74 @@
       base_url: 'https://<customer>.staging.assembly-api.com/api/',
       api_key: '<key>'
     )
 
     u = Chord::User.find(1)                   # fetch user
-    u.attributes                              # see attributes hash
-    u.update(name: 'New Name', notes: 'Etc')  # update attributes
-    u.update(metadata: {ambassador_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)
+    u.email                                   # view an attribute
+    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?
+
+For complete/current list of supported objects and methods, please see the code.
+
+
+## Querying
+
+The most basic way to get a collection of objects:
+
+    Chord::Order.all
+
+You can also filter and sort, though the parameters are not well documented:
+
+    Chord::Order.where(
+      'q[completed_at_gt]' => '2022-09-14',
+       'q[s]' => 'completed_at desc'
+    )
+
+
+## Object attributes
+
 Objects are constructed in a way that minimizes API calls but occasionally yields objects that seem incomplete. For example:
 
     orders = Chord::Order.all
     o = orders.first
 
-will return a Chord::Order object with around 40 attributes, not the full set of 55 (it's missing line items, for example), because the `/orders` endpoint returns abbreviated objects. To load the full set of data for these objects, use the `expand!` method:
+will return a Chord::Order object with around 40 attributes, not the full set of 55 (it's missing line items, for example), because the `/orders` endpoint returns abbreviated objects. To load the full set of data for such an object, use the `expand!` method:
 
     o.expand!
+
+
+# Configuration options
+
+To get your sensitive config data out of your code, you can put it in a YAML file, like so:
+
+    # chord_config.yml
+    base_url: https://...
+    api_key: ...
+
+and load it by calling:
+
+    Chord.config_from_file('chord_config.yml')
+
+Or you can put your configuration in environment variables:
+
+    CHORD_BASE_URL=https://...
+    CHORD_API_KEY=...
+
+and load it by calling:
+
+    Chord.config_from_env
+
+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')