diff --git a/components/mdx-components/p.js b/components/mdx-components/p.js
index 6067b8267..1d1b95611 100644
--- a/components/mdx-components/p.js
+++ b/components/mdx-components/p.js
@@ -6,6 +6,16 @@ const P = styled.p`
   font-weight: 400;
   line-height: 1.6;
   margin: 16px 0;
+  
+  img + em { 
+    display: block; 
+    text-align: center;
+    color: #666666;
+    font-style: normal;
+    font-size: 14px;
+    margin: 5px 0 10px;
+    display: block;
+  } 
 `;
 
 export default P;
\ No newline at end of file
diff --git a/data/guides/design-patterns-for-humans.md b/data/guides/design-patterns-for-humans.md
index ed5d8ecab..5f3a049b0 100644
--- a/data/guides/design-patterns-for-humans.md
+++ b/data/guides/design-patterns-for-humans.md
@@ -32,9 +32,11 @@ Serverful apps need to run consistently, watching for requests. Then, when reque
 Serverful apps need to run consistently, watching for requests. Then, when requested, the app handles the request itself. In serverful monolith style apps, routing is commonly handled by a single file. Let's look at an Express.js example to illustrate this:
 
 ![](https://endler.dev/2019/tinysearch/bloomfilter.svg)
+*A picture taken from endler.dev*
 
 Our team runs a number of typical services for monitoring and performance analysis: API endpoints for metrics written in Go, Prometheus exporters, log parsers like Logstash or Gollum, and databases like InfluxDB or Elasticsearch. Each of these services run in their own container. We needed a simple system to keep those jobs running.
 
+
 We started with a list of requirements for container orchestration:
 
 * Run a fleet of services across many machines.