3 files changed, 6 insertions, 6 deletions

diff --git a/docs/Crypto.txt b/docs/Crypto.txt
index 11653616..d53c16a8 100644
--- a/docs/Crypto.txt
+++ b/docs/Crypto.txt
@@ -51,8 +51,8 @@ Connecting to an already added friend:
     Data packet:
         [char with a value of 03][Encrypted data]
     Each data packet received it is decrypted using the secret nonce sent to the other(with +1 added for the first packet +2 for the second, etc...)
-    along with the private session key of the reciever.
+    along with the private session key of the receiver.
     Every data packet sent is encrypted using the secret nonce we received (with +1 added for the first packet +2 for the second, etc...),
-    the session public key of the reciever and the session private key of the sender.
+    the session public key of the receiver and the session private key of the sender.
     
     The encrypted connection is only deemed successful when the empty data packet is received and decrypted successfully.
diff --git a/docs/IDEAS.txt b/docs/IDEAS.txt
index c00b242e..d1be2ce6 100644
--- a/docs/IDEAS.txt
+++ b/docs/IDEAS.txt
@@ -14,6 +14,7 @@ A couple of ideas posted in the threads.
 
 - ability to log in with username and password
     possible implementation: store keys in a server and use user/pass to retrieve keys from server transparently
+   >too centralized
 - looking up people and adding as contacts, etc by name or username
     possible implementation: store pubkey-hash/info correspondences in a public directory, integrate access into client
 - portable contact list/profile/other account data
@@ -21,7 +22,6 @@ A couple of ideas posted in the threads.
 - POSSIBLY interfacing with regular phones. probably not possible, but plebs might complain (THIS IS EXPENSIVE (hence 'probably not possible')) <3
 
 IMPORTANT: release two major sanctioned UIs, one for autists, one with inbuilt support for the previous list so that plebs can't get confused with setting it up and autists don't complain about it getting in their way. de geso
-
-
+    > I would suggest a "Advanced options" where the autists can rejoice with all kinds of options (and it doesn't frighten the normalfags, since it's not shown by default). Also, 2 UIs would be chaos to maintain.
 ##############
 
diff --git a/docs/Lossless_UDP.txt b/docs/Lossless_UDP.txt
index bbfd2ad1..1159feb6 100644
--- a/docs/Lossless_UDP.txt
+++ b/docs/Lossless_UDP.txt
@@ -53,7 +53,7 @@ Lossless UDP:
                     If the handshake was done:
                         Start sending SYNC packets.
                 Add +1 to the counter of the SYNC packets we send.
-                Check to see if any packets were dropped when sending them to us (compare sent_packetnum with the number of packets we recieved.)
+                Check to see if any packets were dropped when sending them to us (compare sent_packetnum with the number of packets we received.)
                     If some were, The next SYNC packets we send will be request packets requesting the missing packets.
                 Check if the other client received what we sent him (compare recv_packetnum with the number of packets we sent) and clear them from the buffer.
                 If the packet is a request packet.
@@ -81,7 +81,7 @@ Lossless UDP:
 
         Keep track of the percent of packets dropped, if it is too high, lower the send rate. If it is low, increase it.
                 
-        Have a send packets buffer that we can write to and a recieved packets buffer that we can read from.
+        Have a send packets buffer that we can write to and a received packets buffer that we can read from.