From 9a2931969b3e55657324082ce8f22e98859bed07 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=C5=81ukasz=20Gandecki?=
 <4002543+lgandecki@users.noreply.github.com>
Date: Fri, 10 Jul 2020 17:32:44 +0200
Subject: [PATCH] typo, unnecessary duplication of a word

---
 .tortilla/manuals/templates/step12.tmpl | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/.tortilla/manuals/templates/step12.tmpl b/.tortilla/manuals/templates/step12.tmpl
index a05c46be..ea6c4f85 100644
--- a/.tortilla/manuals/templates/step12.tmpl
+++ b/.tortilla/manuals/templates/step12.tmpl
@@ -56,7 +56,7 @@ And then we will update the `cache.service` to write the broadcasted chat to the
 
 Now we can create new chats, and the chats list would be updated, without refreshing the page. You can also test it with 2 separate sessions in the browser and see how each tab/window affects the other. Lastly, we will implement a chat removal function. This is important as we don’t want to garbage our chats collection, sometimes we would like to clean up some of them.
 
-In the back-end, let’s implement the `removeChat` mutation. The chat can only be removed only if the current user is one of the chat’s participants. The mutation will also remove all the messages which are related to the target chat, since we’re not gonna use them anymore. The chat will be removed for all participants. This is not exactly the behavior of the original Whatsapp, but to keep things simple we will go with that solution:
+In the back-end, let’s implement the `removeChat` mutation. The chat can be removed only if the current user is one of the chat’s participants. The mutation will also remove all the messages which are related to the target chat, since we’re not gonna use them anymore. The chat will be removed for all participants. This is not exactly the behavior of the original Whatsapp, but to keep things simple we will go with that solution:
 
 {{{ diffStep 9.4 module="server" }}}