From 69fbe04af6acc74f38156ed90c657ae800d533aa Mon Sep 17 00:00:00 2001
From: Danil <37103154+Danyylka@users.noreply.github.com>
Date: Mon, 2 Dec 2024 18:56:20 +0100
Subject: [PATCH] Fix spelling error (#15144)

Update CONTRIBUTING.md
---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 660f4b4f986..09d7d0863a8 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -34,7 +34,7 @@ We also maintain a production branch which is used to deploy to ... production!
 
 If needed, we can also deploy specific versions to production. For this is recommended approach is to open a new pull request against the production branch containing **only** the commits to be deployed since the latest production deploy. One way to do this is to rebase a local production-fix branch against the remote production branch and cherry pick the commits to be deployed from master. After this is a pull request is made and has to be approved by some of our team members. Once approved the updated production branch is immediately deployed.
 
-#### Execptions
+#### Exceptions
 
 Both wedlocks (email service) and unlock-protocol-com (static site) are deployed to production from the `master` branch. They do not have a staging environment.