Fix several typos in the docs.

Thanks Mopi!

3 files changed, 6 insertions, 6 deletions

diff --git a/doc/source/dev/contributing.rst b/doc/source/dev/contributing.rst
index ca7de049..8d386c87 100644
--- a/doc/source/dev/contributing.rst
+++ b/doc/source/dev/contributing.rst
@@ -5,7 +5,7 @@ Conventions
 -----------
 
 We don’t have a strict set of conventions, but you should respect PEP8 mostly
-(e.g. 4 spaces, class names in CamelCase and methods lowercased with
+(e.g. 4 spaces, class names in CamelCase and methods lowercase with
 underscores) except if it means less-readable code (80 chars is often a hassle,
 and if you look inside poezio you’ll see lots of long lines, mostly because of
 strings).
@@ -18,7 +18,7 @@ for the application as a whole.
 Commit guidelines
 -----------------
 
-Commits **should** have a meaninful title (first line), and *may* have a detailed
+Commits **should** have a meaningful title (first line), and *may* have a detailed
 description below. There are of course exceptions (for example, a single-line
 commit that takes care of a typo right behind a big commit does not need to
 say ``fix a typo ("azre" → "are") in toto.py line 45454``, since the metainfos
diff --git a/doc/source/dev/overview.rst b/doc/source/dev/overview.rst
index fcf5ff22..96d4435b 100644
--- a/doc/source/dev/overview.rst
+++ b/doc/source/dev/overview.rst
@@ -40,7 +40,7 @@ method (inherited empty from the Tab class), call a scrolling method from the
 appropriate **window**.
 
 All tabs types inherit from the class **Tab**, and the tabs featuring
-chat functionnality will inherit from **ChatTab** (which inherits from **Tab**).
+chat functionality will inherit from **ChatTab** (which inherits from **Tab**).
 
 Examples of **tabs**: MUCTab, XMLTab, RosterTab, MUCListTab, etc…
 
@@ -80,9 +80,9 @@ or
 
     /command "arg1 with spaces" arg2
 
-However, when creating a command, you wil deal with _one_ str, no matter what.
+However, when creating a command, you will deal with _one_ str, no matter what.
 There are utilities to deal with it (common.shell_split), but it is not always
-necessary. Commands are registered in the **commands** dictionnary of a tab
+necessary. Commands are registered in the **commands** dictionary of a tab
 structured as key (command name) -> tuple(command function, help string, completion).
 
 Completions are a bit tricky, but it’s easy once you get used to it:
diff --git a/doc/source/dev/xep.rst b/doc/source/dev/xep.rst
index 339553ff..7feca4cf 100644
--- a/doc/source/dev/xep.rst
+++ b/doc/source/dev/xep.rst
@@ -91,7 +91,7 @@ Table of all XEPs implemented in poezio.
 +----------+-------------------------+---------------------+
 |0270      |Compliance Suites 2010   |Advanced Client      |
 +----------+-------------------------+---------------------+
-|0280      |Messsage Carbons         |100%                 |
+|0280      |Message Carbons          |100%                 |
 +----------+-------------------------+---------------------+
 |0296      |Best Practices for       |0%                   |
 |          |Resource Locking         |                     |