From 5bd6729443b5344038ca6ef047ce3b2c983b01b1 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Roberto=20Abdelkader=20Mart=C3=ADnez=20P=C3=A9rez?=
 <robertomartinezp@gmail.com>
Date: Wed, 18 Dec 2019 17:04:22 +0100
Subject: [PATCH] Italize the word "Kapow!"

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 10c63f5..5f9a20e 100644
--- a/README.md
+++ b/README.md
@@ -12,7 +12,7 @@
 
 ---
 
-## What's Kapow!
+## What's *Kapow!*
 
 Say we have a nice cozy **shell command** that solves our problem. *Kapow!* lets
 us easily **turn that into an HTTP API**.
@@ -30,7 +30,7 @@ kapow route add /apache-errors - <<-'EOF'
 EOF
 ```
 
-and then, run it using Kapow!
+and then, run it using *Kapow!*
 
 ```bash
 [apache-host]$ kapow server --bind 0.0.0.0:8080 search-apache-errors.pow
@@ -46,7 +46,7 @@ finally, we can read from the just-defined endpoint:
 ...
 ```
 
-### Why Kapow! shines in these cases
+### Why *Kapow!* shines in these cases
 
 - We can share information **without having to grant SSH access** to anybody.
 - We can share information easily **over HTTP**.