Edited 075_Inside_a_shard/10_Intro.asciidoc with Atlas code editor

075_Inside_a_shard/10_Intro.asciidoc

@@ -1,12 +1,12 @@
 [[inside-a-shard]]
-== Inside a shard
+== Inside a Shard
 
 In <<distributed-cluster>>, we introduced the _shard_, and described((("shards"))) it as a
-low-level ``worker unit''. But what exactly *is* a shard and how does it work?
-In this chapter we will answer these questions:
+low-level _worker unit_. But what exactly _is_ a shard and how does it work?
+In this chapter, we answer these questions:
 
-* Why is search _**near** real-time_?
-* Why are document CRUD (_create-read-update-delete_) operations _**real**-time_?
+* Why is search _near_ real-time?
+* Why are document CRUD (create-read-update-delete) operations _real-time_?
 * How does Elasticsearch ensure that the changes you make are durable, that
   they won't be lost if there is a power failure?
 * Why does deleting documents not free up space immediately?
@@ -15,15 +15,15 @@ In this chapter we will answer these questions:
 
 The easiest way to understand how a shard functions today is to start with a
 history lesson. We will look at the problems that needed to be solved in order
-to provide a distributed durable datastore with near real-time search and
+to provide a distributed durable datas tore with near real-time search and
 analytics.
 
-.Content warning
+.Content Warning
 ****
 
-The information presented below is for your interest. You are not required to
+The information presented in this chapter is for your interest. You are not required to
 understand and remember all the detail in order to use Elasticsearch. Read
-the section to gain a taste for how things work, and to know where the
+this chapter to gain a taste for how things work, and to know where the
 information is in case you need to refer to it in the future, but don't be
 overwhelmed by the detail.