service/donate.md

@@ -294,7 +294,7 @@ to Tor's mission. The general idea is that the more roadblocks you put
 in the way of a donation, the more likely it is that card testers will
 pick someone else to card test. These techniques usually result in
 blocking users of the tor network or tor browser, either as a primary
-or seide effect.
+or side effect.
 
 - Using cloudflare
 - Forcing donors to create an account
@@ -305,7 +305,7 @@ However, we have identified some techniques that do work, with minimal
 impact to our legitimate donors.
 
 - Rate limiting donations
-- pre-emptively blocking IP ranges in firewalls
+- preemptively blocking IP ranges in firewalls
 - Metrics
 
 An example of rate limiting looks something like this: Allow users to
@@ -1015,7 +1015,7 @@ real sandboxing or containerization. There was an attempt to set up the runner
 using systemd-nspawn, but it was taking too long and we
 [eventually decided against it][].
 
-Currently, project members with `Developper` permission or above in the
+Currently, project members with `Developer` permission or above in the
 donate-neo project may edit the CI configuration to execute arbitrary commands
 as the `gitlab-runner` user on the machine. Since these users are all trusted
 contributors, this should pose no problem. However, care should be taken to