diff --git a/specs/kilo/fifo-optional.rst b/specs/kilo/fifo-optional.rst
index 4b219f9..011a14b 100644
--- a/specs/kilo/fifo-optional.rst
+++ b/specs/kilo/fifo-optional.rst
@@ -16,7 +16,7 @@ Make FIFO guarantee optional
 FIFO has been one of Zaqar's most wanted guarantees. Besides
 reliability, durability and other latency requirements, users have
 always requested FIFO to be there. This feature, however, has proven
-to be an issue for some scenarios that don't necesarily require it,
+to be an issue for some scenarios that don't necessarily require it,
 hence this proposal.
 
 https://blueprints.launchpad.net/zaqar/+spec/make-fifo-optional
diff --git a/specs/newton/mistral-notifications.rst b/specs/newton/mistral-notifications.rst
index 5dc2331..976bec5 100644
--- a/specs/newton/mistral-notifications.rst
+++ b/specs/newton/mistral-notifications.rst
@@ -60,9 +60,9 @@ as well as a number of other actions (some of which, like sending email and
 webhooks, are similar to Zaqar's notifications).
 
 The missing link to build fully autonomous applications is for messages
-(potentially, but not neccessarily originating from the OpenStack cloud itself)
+(potentially, but not necessarily originating from the OpenStack cloud itself)
 on Zaqar queues to be able to trigger Mistral workflows (potentially, but not
-neccessarily calling other OpenStack APIs). This would give developers of cloud
+necessarily calling other OpenStack APIs). This would give developers of cloud
 applications an extremely flexible way of plugging together event-driven,
 application-specific, autonomous actions.