diff --git a/guidelines/raising-an-issue.md b/guidelines/raising-an-issue.md
index d0c046f8..9934c826 100644
--- a/guidelines/raising-an-issue.md
+++ b/guidelines/raising-an-issue.md
@@ -11,6 +11,6 @@ Issues specific to a project should first be raised within the project itself. E
 
 There are several ways you can bring up an issue to the TOC. The most direct one is to simply open an issue in [the TOC GitHub repository](https://github.com/hyperledger/toc/issues) or to send an email to [the TOC mailing list](https://lists.hyperledger.org/g/toc/). Projects also submit [quarterly reports PRs](https://github.com/hyperledger/toc/pulls?q=is%3Aopen+is%3Apr+label%3Aquarterly-report) against which you can file a comment. Either way should get attention from the TOC.
 
-Please, provide all relevant background information when raising an issue so that the TOC is fully equiped to process it. Failing to do so will lead the TOC to ask for that information as a first step and delay processing.
+Please, provide all relevant background information when raising an issue so that the TOC is fully equipped to process it. Failing to do so will lead the TOC to ask for that information as a first step and delay processing.
 
 If you are unsure about how to proceed or would like to raise an issue privately consider contacting one of the [Hyperledger Community Architects](https://wiki.hyperledger.org/display/CA/Community+Architects+Team) or one of the [TOC members](../members-info/toc-members.md). Community Architects can easily be contacted via email [community-architects@hyperledger.org](mailto:community-architects@hyperledger.org) or chat [#community-architects](https://discord.com/servers/hyperledger-foundation-905194001349627914).