Update docs for review comments

docs/tempo/website/operations/deployment.md

@@ -68,28 +68,17 @@ each instance are aware of each other; this is known as clustering.  The
 components form a [consistent hash ring]({{< relref "./consistent_hash_ring"
 >}}) to coordinate operations among the multiple Tempo instances.
 
-The configuration of a scalable single binary defines `kvstore`.  Here is an
-example `memberlist` configuration:
-
-```yaml
-target: scalable-single-binary
-ingester:
-  lifecycler:
-    ring:
-      kvstore:
-        store: memberlist
-```
-
-Additionally, the `queriers` must know the DNS name that will contain the addresses of all other instances.
-For example:
+The `queriers` must know the DNS name that will contain the addresses of all
+other instances.  For example:
 
 ```yaml
 querier:
   frontend_worker:
     frontend_address: tempo.lab.example.com:9095
 ```
 
-Each of the `queriers` will perform a DNS lookup for the `frontend_address` and connect to the addresses found within the DNS record.
+Each of the `queriers` will perform a DNS lookup for the `frontend_address` and
+connect to the addresses found within the DNS record.
 
 Find a docker-compose deployment example at: