Fix some typos

Author: captain toad (bee)

README.md

@@ -1,6 +1,6 @@
 # NetPass' official website!
 This repository contains the source code of NetPass' website, available [here!](https://netpass.cafe)
 
-You can find the dev builds [here](https://lnlenost.github.io/NetPassWebsite)...  but they are highly unstable, so I reccomend sticking onto the prod build!
+You can find the dev builds [here](https://lnlenost.github.io/NetPassWebsite)...  but they are highly unstable, so I recommend sticking onto the production build!
 
 Check out our Privacy Policy [here](https://lnlenost.github.io/NetPassWebsite/www/privacy.html)

www/privacy.html

@@ -22,7 +22,7 @@
     <main>
         <section>
             <h2>NetPass Privacy Policy</h2>
-<p>We take the privacy of our users seriously. As such, we collect the <b>minimum amount of data</b> required to operate our service. Below you can read about which data is stored, why and for how long.</p>
+<p>We take the privacy of our users seriously. As such, we collect the <b>minimum amount of data</b> required to operate our service. Below you can read about which data is stored, why it's stored, and for how long.</p>
 </section>
 <section>
 <h2>Cookies</h2>
@@ -32,14 +32,14 @@ <h2>Cookies</h2>
 This Cookie is used to identify the user between page loads, so that the server knows who you are while you access and edit your profile. This is a short-lived session cookie.</p>
 
 <p><strong>Auth Cookies:</strong><br>
-These cookies are cookies that are used during authentification to prevent an attacker to gain control of your identity. These are short-lived session cookies.</p>
+These cookies are cookies that are used during authentication to prevent an attacker to gain control of your identity. These are short-lived session cookies.</p>
 </section>
 <section>
 <h2>Data</h2>
 <p>We collect various bits of data to make the service work:</p>
 
 <p><strong>Identifying bits:</strong><br>
-To identify the console connecting to NetPass, we store the consoles mac address together with a console-unique hash consisting out of the <a href="https://www.3dbrew.org/wiki/AM:GetDeviceId">device id</a> and the mac. While the mac is stored in plain text, it does not seem feasable to do otherwise, as throughout the StreetPass protocol the mac address of a user apears in the transmitted payloads frequently.<br>
+To identify the console connecting to NetPass, we store the consoles mac address together with a console-unique hash consisting out of the <a href="https://www.3dbrew.org/wiki/AM:GetDeviceId">device id</a> and the mac. While the mac is stored in plain text, it does not seem feasible to do otherwise, as throughout the StreetPass protocol the mac address of a user appears in the transmitted payloads frequently.<br>
 For background collection of passes to work, we also store the BOSS UID, as that is needed to identify the console when doing StreetPass-Relay requests. These identifying bits are stored indefinitely.<br>
 For some integrations to work, we additionally store your friends code. This friends code is not shared with third-party services; you will have to supply your friends code to the other service somehow, if it needs that.</p>
 
@@ -53,7 +53,7 @@ <h2>Data</h2>
 When you used the Back Alley to get a specific pass, the time of when this is happening is stored on the server. This is to prevent cheating by using the back alley more frequently than intended. These time entries are stored for up to 3 days.</p>
 
 <p><strong>Bans:</strong><br>
-When you are issued a ban, the reason for the ban and the time when it expires is stored indefinitely. This is to be able to enforce the ban and to be able to provide moderators a history of when and why a ban occured, to be able to detect repeat offenses.</p>
+When you are issued a ban, the reason for the ban and the time when it expires is stored indefinitely. This is to be able to enforce the ban and to be able to provide moderators a history of when and why a ban occurred, to be able to detect repeat offenses.</p>
 
 <p><strong>Integrations:</strong><br>
 For integrations to function, the HTTP headers that the console sends on StreetPass-Relay requests are stored, so that those can then be sent off to the integration. This data is stored indefinitely.<br>
@@ -82,7 +82,7 @@ <h2>Data Sharing</h2>
 <p><strong>Third-Party identifiers:</strong><br>
 If you decide to identify yourself with a third-party service, the service will know that you tried to identify with it. The service will never receive any data from NetPass itself, meaning we do not give any data to them</p>
 <p><strong>Integrations:</strong><br>
-For integrations to work, the StreetPass-Relay HTTP headers your console uploaded are being transfered to the third-party service. This includes your consoles BOSS UID.</p>
+For integrations to work, the StreetPass-Relay HTTP headers your console uploaded are being transferred to the third-party service. This includes your consoles BOSS UID.</p>
 </section>
 <section>
 <h2>Contact</h2>

www/rules.html

@@ -35,7 +35,7 @@ <h2>2. Keep things PG-13</h2>
         </p>
         <h2>3. No Piracy</h2>
         <p>
-<b>Do not discuss piracy or anything relating to piracy.</b> Do not ask how to pirate games/updates/dlcs, firmware dumps, SDK's for consoles, etc. Do not share, discuss, hint or guide towards downloads links or tools which promote or encourage the use of piracy. 
+<b>Do not discuss piracy or anything relating to piracy.</b> Do not ask how to pirate games/updates/dlcs, firmware dumps, SDK's for consoles, etc. Do not share, discuss, hint or guide towards downloads, links, or tools which promote or encourage the use of piracy. 
         </p>
         <h2>4. Sensitive Data</h2>
         <p>