From e1a15b14bf206cd64ec7a71a846947eaceaf0b1f Mon Sep 17 00:00:00 2001
From: Hsu Still <341464@gmail.com>
Date: Thu, 28 Sep 2017 11:27:50 +0800
Subject: [PATCH] Change `add-ons` to `addons` for consistency

---
 docs/guides/getting_started/installing.md  | 2 +-
 docs/guides/getting_started/terminology.md | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/guides/getting_started/installing.md b/docs/guides/getting_started/installing.md
index 66aa6f8ba..5d4c85d81 100644
--- a/docs/guides/getting_started/installing.md
+++ b/docs/guides/getting_started/installing.md
@@ -27,7 +27,7 @@ required. When using .NET Framework, it is suggested to target
 Release builds of Discord.Net 1.0 will be published to the
 [official NuGet feed].
 
-Development builds of Discord.Net 1.0, as well as add-ons *(TODO)* are
+Development builds of Discord.Net 1.0, as well as addons *(TODO)* are
 published to our development [MyGet feed].
 
 Direct feed link: `https://www.myget.org/F/discord-net/api/v3/index.json`
diff --git a/docs/guides/getting_started/terminology.md b/docs/guides/getting_started/terminology.md
index e9d535eec..74f7a6259 100644
--- a/docs/guides/getting_started/terminology.md
+++ b/docs/guides/getting_started/terminology.md
@@ -23,8 +23,8 @@ but you should be aware of the differences between them.
 `Discord.Net.Core` provides a set of interfaces that models Discord's 
 API. These interfaces are consistent throughout all implementations of 
 Discord.Net, and if you are writing an implementation-agnostic library 
-or add-on, you can rely on the core interfaces to ensure that your 
-add-on will run on all platforms.
+or addon, you can rely on the core interfaces to ensure that your 
+addon will run on all platforms.
 
 `Discord.Net.Rest` provides a set of concrete classes to be used 
 **strictly** with the REST portion of Discord's API. Entities in this