From c524b4ecc30911dc540298f6d6599931a0d6eb62 Mon Sep 17 00:00:00 2001
From: nagubal <45527+nagubal@users.noreply.github.com>
Date: Fri, 21 Feb 2020 14:51:30 +0100
Subject: [PATCH] Typo correction: opossite => opposite (#12152)

A simple type correction
---
 source/_integrations/cover.mqtt.markdown | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/source/_integrations/cover.mqtt.markdown b/source/_integrations/cover.mqtt.markdown
index 8f2b661dbbff..1440b4894c8b 100644
--- a/source/_integrations/cover.mqtt.markdown
+++ b/source/_integrations/cover.mqtt.markdown
@@ -18,7 +18,7 @@ The device state (`open` or `closed`) will be updated only after a new message i
 For this purpose is `position_topic` which can set state of the cover and position.
 Default setting are 0 means the device is `closed` and all other intermediate positions means the device is `open`.
 `position_topic` is managed by `position_open` and `position_closed`
-You can set it up in opossite way as well.
+You can set it up in opposite way as well.
 If position topic is defined than state topic is ignored.
 
 If a state topic and position topic are not defined, the cover will work in optimistic mode. In this mode, the cover will immediately change state (`open` or `closed`) after every command sent by Home Assistant. If a state topic/position topic is defined, the cover will wait for a message on `state_topic` or `position_topic`.