Fixing typos

dynamoose · Dec 11, 2021 · 2f07a06 · 2f07a06
1 parent 1d145bb
commit 2f07a06
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/SECURITY.md b/SECURITY.md
@@ -10,9 +10,9 @@ While reading this document, please remember that the [LICENSE](https://github.c
 
 The following versions will get security updates if necessary. Security updates will be included in either patch or minor versions.
 
-In the event a security vulnerability is patched in a major version, it will also be backported to all supported version lines (in the event the vulnerability exists on previous version line).
+In the event a security vulnerability is patched in a major version, it will also be back-ported to all supported version lines (in the event the vulnerability exists on previous version line).
 
-Security vulnerabilities will only be backported to previous minor versions in the extremely unlikely event a minor version causes a breaking change and someone requests the patch to be backwards applied, and demonstrates the breaking change. If this occurs please [contact me](https://charlie.fish/contact) with your request.
+Security vulnerabilities will only be back-ported to previous minor versions in the extremely unlikely event a minor version causes a breaking change and someone requests the patch to be backwards applied, and demonstrates the breaking change. If this occurs please [contact me](https://charlie.fish/contact) with your request.
 
 | Version | Supported          |
 | ------- | ------------------ |
@@ -27,8 +27,8 @@ For security purposes, please follow the following guidelines:
 
 1. Ensure all sites you access while reporting a vulnerability are accessed using SSL/HTTPS.
 2. Encrypt all vulnerability information using my [Keybase](https://keybase.io/fishcharlie) (Keybase link can also be found on my contact page) encryption keys.
-3. For ease of use, please include a method to contact you unencrypted in your message. In the event decryption of your message fails, I need a way to contact you to notify you of the decryption failure.
+3. For ease of use, please include a method to contact you un-encrypted in your message. In the event decryption of your message fails, I need a way to contact you to notify you of the decryption failure.
 
-You can expect to receive an initial receipt of your report within 48 business hours of submission (exception to this is holiday periods). In the event you don't receive an initial receipt of your report within that timeframe please contact me again (I suggest using unencrypted communication for this second communication, but the choice is yours).
+You can expect to receive an initial receipt of your report within 48 business hours of submission (exception to this is holiday periods). In the event you don't receive an initial receipt of your report within that time frame please contact me again (I suggest using un-encrypted communication for this second communication, but the choice is yours).
 
 During the vulnerability process, I will keep you informed and may ask follow up questions regarding your report, so please ensure you remain available until a fix is deployed.
diff --git a/SPONSOR.md b/SPONSOR.md
@@ -16,7 +16,7 @@ There are two different ways you can help to fund Dynamoose. Both are listed bel
 
 You can sponsor me (Charlie Fish) directly. I'm the primary maintainer/contributor of Dynamoose, and the majority of the time I spend on open source projects goes towards working on Dynamoose. Therefore any contributions I receive directly helps support my work on my open source projects (Dynamoose being the largest and the one I spend most time on).
 
-This is benefical since GitHub Sponsors charges very little in terms of fees (at the time of writing I've been charged no fees). Which means more of your funds are going directly to support me and the project. Plus you get some extra perks such as a sponsor badge.
+This is beneficial since GitHub Sponsors charges very little in terms of fees (at the time of writing I've been charged no fees). Which means more of your funds are going directly to support me and the project. Plus you get some extra perks such as a sponsor badge.
 
 **This is the recommended option.**
 
@@ -26,7 +26,7 @@ This is benefical since GitHub Sponsors charges very little in terms of fees (at
 
 You can also sponsor the project through Open Collective.
 
-This is benefical to track the project funding, and has full transparancy into how the funds are being used. At the time of writing this, it also has the benefit of more specific funding amounts (since GitHub Sponsors doesn't let you enter a custom amount). You can also do one time donations through Open Collective (which as of writing this you can not due on GitHub Sponsors).
+This is beneficial to track the project funding, and has full transparency into how the funds are being used. At the time of writing this, it also has the benefit of more specific funding amounts (since GitHub Sponsors doesn't let you enter a custom amount). You can also do one time donations through Open Collective (which as of writing this you can not due on GitHub Sponsors).
 
 However, Open Collective has much higher fees (compared to GitHub Sponsors), which means less of the funds get to us. After opening the Open Collective account a $5 donation had $0.95 worth of fees attached to it (which is quite a bit).