configuration.md in table_sync-6.0.2

- old
+ new

@@ -127,10 +127,10 @@
 One possible way of using it is defining a headers exchange and routing rules based on key-value pairs (which correspond to sent headers).
 
 Example:
 
 ```ruby
-TableSync.routing_metadata_callable = -> (klass, attributes) { attributes.slice("project_id") }
+TableSync.headers_callable = -> (klass, attributes) { attributes.slice("project_id") }
 ```
 
 ## Other
 
 - `TableSync.exchange_name` defines the exchange name used for publishing (optional, falls back to default Rabbit gem configuration).