Update README.md to reflect api change from autoCache to 'streamTable'

Author: pellse

README.md

@@ -448,7 +448,7 @@ var assembler = assemblerOf(Transaction.class)
 ### Stream Table
 In addition to the cache mechanism provided by the `cached()` and `cachedMany()` functions, ***Assembler*** also provides a mechanism to automatically and asynchronously update the cache in real-time as new data becomes available via the `streamTable()` function. This ensures that the cache is always up-to-date and avoids in most cases the need for `cached()` to fall back to fetch missing data.
 
-The Stream Table mechanism in ***Assembler*** (via `streamTable()`) can be seen as being conceptually similar to a `KTable` in Kafka. Both mechanisms provide a way to keep a key-value store updated in real-time with the latest value per key from its associated data stream. However, ***Assembler*** is not limited to just Kafka data sources and can work with any data source that can be consumed in a reactive stream.
+The Stream Table mechanism in ***Assembler*** (via `streamTable()`) can be seen as being conceptually similar to a `KTable` in Kafka. Both mechanisms provide a way to keep a key-value store updated in real-time with the latest value per key from its associated data stream. However, ***Assembler*** is not only limited to Kafka data sources and can work with any data source that can be consumed in a reactive stream.
 
 This is how `streamTable()` connects to a data stream and automatically and asynchronously update the cache in real-time: