diff --git a/docs/securing_client_connection.rst b/docs/securing_client_connection.rst index 9ab5d15886..83e0b2a76f 100644 --- a/docs/securing_client_connection.rst +++ b/docs/securing_client_connection.rst @@ -66,7 +66,6 @@ configuration and then go over the configuration options one by one: ``open /Applications/Python\ 3.9/Install\ Certificates.command`` - See this `StackOverflow answer `__ for more information. Enabling TLS/SSL ^^^^^^^^^^^^^^^^ diff --git a/docs/using_python_client_with_hazelcast.rst b/docs/using_python_client_with_hazelcast.rst index cbc7e2983a..fd93adb669 100644 --- a/docs/using_python_client_with_hazelcast.rst +++ b/docs/using_python_client_with_hazelcast.rst @@ -808,11 +808,6 @@ After that, once Client-1 comes back alive, its write request will be rejected by the external service, and only Client-2 will be able to safely talk to it. -.. figure:: https://docs.hazelcast.com/hazelcast/latest/_images/FencedLock.png - :alt: CP Fenced Lock diagram - - CP Fenced Lock diagram - You can read more about the fencing token idea in Martin Kleppmann’s “How to do distributed locking” blog post and Google’s Chubby paper.