sentinel-clients.md delete refs to old versions and redis google group,

valkey-io#132

Signed-off-by: Viktor Söderqvist <[email protected]>

topics/sentinel-clients.md

@@ -67,8 +67,6 @@ Once the client discovered the address of the master instance, it should
 attempt a connection with the master, and call the `ROLE` command in order
 to verify the role of the instance is actually a master.
 
-If the `ROLE` commands is not available (it was introduced in Redis OSS 2.8.12), a client may resort to the `INFO replication` command parsing the `role:` field of the output.
-
 If the instance is not a master as expected, the client should wait a short amount of time (a few hundreds of milliseconds) and should try again starting from Step 1.
 
 Handling reconnections
@@ -84,7 +82,7 @@ In the above cases and any other case where the client lost the connection with
 Sentinel failover disconnection
 ===
 
-Starting with Redis OSS 2.8.12, when Valkey Sentinel changes the configuration of
+When Valkey Sentinel changes the configuration of
 an instance, for example promoting a replica to a master, demoting a master to
 replicate to the new master after a failover, or simply changing the master
 address of a stale replica instance, it sends a `CLIENT KILL type normal`
@@ -151,8 +149,3 @@ document in order to resolve the new Valkey master (or replica) address.
 However update messages received via Pub/Sub should not substitute the
 above procedure, since there is no guarantee that a client is able to
 receive all the update messages.
-
-Additional information
-===
-
-For additional information or to discuss specific aspects of this guidelines, please drop a message to the [Valkey Google Group](https://groups.google.com/group/redis-db).