convert img tags to markdown syntax

(cherry picked from commit 4041032)
apache · Jun 7, 2023 · 40365dc · 40365dc
1 parent 9bfd1b1
commit 40365dc
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/docs/design/architecture.md b/docs/design/architecture.md
@@ -29,7 +29,7 @@ Druid has a distributed architecture that is designed to be cloud-friendly and e
 
 The following diagram shows the services that make up the Druid architecture, how they are typically organized into servers, and how queries and data flow through this architecture.
 
-<img src="../assets/druid-architecture.png" width="800"/>
+![](../assets/druid-architecture.png)
 
 The following sections describe the components of this architecture. 
 
@@ -107,7 +107,7 @@ example, a single day, if your datasource is partitioned by day). Within a chunk
 [_segments_](../design/segments.md). Each segment is a single file, typically comprising up to a few million rows of data. Since segments are
 organized into time chunks, it's sometimes helpful to think of segments as living on a timeline like the following:
 
-<img src="../assets/druid-timeline.png" width="800" />
+![](../assets/druid-timeline.png)
 
 A datasource may have anywhere from just a few segments, up to hundreds of thousands and even millions of segments. Each
 segment is created by a MiddleManager as _mutable_ and _uncommitted_. Data is queryable as soon as it is added to

diff --git a/docs/design/processes.md b/docs/design/processes.md
@@ -43,7 +43,7 @@ Druid processes can be deployed any way you like, but for ease of deployment we
 * **Query**
 * **Data**
 
-<img src="../assets/druid-architecture.png" width="800"/>
+![](../assets/druid-architecture.png)
 
 This section describes the Druid processes and the suggested Master/Query/Data server organization, as shown in the architecture diagram above.