diff --git a/docs/guides/commands/post-execution.md b/docs/guides/commands/post-execution.md
index eb06adde4..227cc02df 100644
--- a/docs/guides/commands/post-execution.md
+++ b/docs/guides/commands/post-execution.md
@@ -104,7 +104,7 @@ have not talked about what to do if the command enters a catastrophic
 failure (i.e., exceptions). To resolve this, we can make use of the
 [CommandService.Log] event.
 
-All exceptions thrown during a command execution are caught and sent 
+All exceptions thrown during a command execution are caught and sent
 to the Log event under the [LogMessage.Exception] property
 as a [CommandException] type. The [CommandException] class allows
 us to access the exception thrown, as well as the context
diff --git a/docs/guides/getting_started/nightlies.md b/docs/guides/getting_started/nightlies.md
index efb69dcff..b54ac11e9 100644
--- a/docs/guides/getting_started/nightlies.md
+++ b/docs/guides/getting_started/nightlies.md
@@ -16,7 +16,7 @@ to our MyGet feed.
 > are generally stable and have more features and bug fixes than
 > the current stable build on NuGet, there **will** be breaking
 > changes during the development or breaking bugs. Although breaking
-> bugs are usually fixed as soon as they are discovered. It is still
+> bugs are usually fixed as soon as they are discovered, it is still
 > important to keep this in mind.
 
 ## Installing with MyGet (Recommended)