From 57f0c0d01baa142e2cd6e010a4dbec6aed177709 Mon Sep 17 00:00:00 2001
From: Sai Kiran Kanuri <saikiranrgda@gmail.com>
Date: Wed, 18 Nov 2020 13:46:26 +0530
Subject: [PATCH] more formatting tests

---
 courses/databases_nosql/key_concepts.md | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/courses/databases_nosql/key_concepts.md b/courses/databases_nosql/key_concepts.md
index 0f45c86..46723d4 100644
--- a/courses/databases_nosql/key_concepts.md
+++ b/courses/databases_nosql/key_concepts.md
@@ -132,7 +132,7 @@ When data is distributed across nodes, it can be modified on different nodes at
 
 
                 
-<p align="center">**Vector clocks illustration**</p>
+<p align="center"><span style="text-decoration:underline;  font-weight:bold;">Vector clocks illustration</span></p>
 
 Vector clocks have the following advantages over other conflict resolution mechanism
 
@@ -172,7 +172,7 @@ When the amount of data crosses the capacity of a single node, we need to think
 ![alt_text]( images/database_sharding.png "Sharding")
 
 
-<p align="center"> **<span style="text-decoration:underline;">Sharding example</span>** </p>
+<p align="center"><span style="text-decoration:underline;  font-weight:bold;">Sharding example</span> </p>
 
 
 ### Hashing
@@ -210,7 +210,7 @@ Say that our hash function h() generates a 32-bit integer. Then, to determine to
 ![alt_text]( images/consistent_hashing.png "Consistent Hashing")
 
 
-<p align="center">**<span style="text-decoration:underline;">Consistent hashing illustration</span>**</p>
+<p align="center"><span style="text-decoration:underline;  font-weight:bold;">Consistent hashing illustration</span></p>
 
 In consistent hashing when a server is removed or added then only the keys from that server are relocated. For example, if server S3 is removed then, all keys from server S3 will be moved to server S4 but keys stored on server S4 and S2 are not relocated. But there is one problem, when server S3 is removed then keys from S3 are not equally distributed among remaining servers S4 and S2. They are only assigned to server S4 which increases the load on server S4.
 
@@ -253,7 +253,7 @@ In a 6 node cluster, you need 4 nodes for a majority.
 
 ![alt_text](images/Quorum.png "image_tooltip")
 
-<p align="center"> <span style="text-decoration:underline;">**Quorum example**</span> </p>
+<p align="center"> <span style="text-decoration:underline; font-weight:bold;">Quorum example</span> </p>
 
 
 
@@ -270,5 +270,5 @@ Below diagram demonstrates Quorum selection on a cluster partitioned into two se
 
 ![alt_text](images/cluster_quorum.png "image_tooltip")
 
-**<p align="center">**Cluster Quorum example</p>**
+**<p align="center"><span style="text-decoration:underline; font-weight:bold;">Cluster Quorum example</span></p>**