Fix typos

contributing.md

@@ -56,7 +56,7 @@ If the module meets the code quality requirements, it may be added to the offici
 
 # JSON Formatting
 
-The ability to add new radio band allocation identifiers and color maps relies on JSON files. Proper formatting of these JSOn files is important for reference and readability. The following guides will show you how to properly format the JSON files for their respective uses.
+The ability to add new radio band allocation identifiers and color maps relies on JSON files. Proper formatting of these JSON files is important for reference and readability. The following guides will show you how to properly format the JSON files for their respective uses.
 
 **IMPORTANT: JSON File cannot contain comments, there are only in this example for clarity**
 
@@ -75,13 +75,13 @@ Please follow this guide to properly format the JSON files for custom radio band
         // Bands in this array must be sorted by their starting frequency
         {
             "name": "Name of the band",
-            "type": "Type name ('amateur', 'broadcast', 'marine', 'military', or any type decalre in config.json)",
+            "type": "Type name ('amateur', 'broadcast', 'marine', 'military', or any type declared in config.json)",
             "start": 148500, //In Hz, must be an integer
             "end": 283500 //In Hz, must be an integer
         },
         {
             "name": "Name of the band",
-            "type": "Type name ('amateur', 'broadcast', 'marine', 'military', or any type decalre in config.json)",
+            "type": "Type name ('amateur', 'broadcast', 'marine', 'military', or any type declared in config.json)",
             "start": 526500, //In Hz, must be an integer
             "end": 1606500 //In Hz, must be an integer
         }    
@@ -98,7 +98,7 @@ Please follow this guide to properly format the JSON files for custom color maps
     "name": "Short name (has to fit in the menu)",
     "author": "Name of the original/main creator of the color map",
     "map": [
-        // These are the color codes, in hexadecimal (#RRGGBB) format, for the custom color scales for the waterfall. They must be entered as strings, not integers, with the hastag/pound-symbol proceeding the 6 digit number. 
+        // These are the color codes, in hexadecimal (#RRGGBB) format, for the custom color scales for the waterfall. They must be entered as strings, not integers, with the hashtag/pound-symbol proceeding the 6 digit number. 
         "#000020",
         "#000030",
         "#000050",

readme.md

@@ -209,7 +209,7 @@ The modules built will be some of the following (Repeat the instructions above f
 ## Select which modules you wish to build
 
 Depending on which module you want to build, you will need to install some additional dependencies.
-Here are listed every module that requires addition dependencies. If a module enabled by default and you do not wish to install a perticular dependency (or can't, eg. the BladeRF module on Debian Buster),
+Here are listed every module that requires addition dependencies. If a module enabled by default and you do not wish to install a particular dependency (or can't, eg. the BladeRF module on Debian Buster),
 you can disable it using the module parameter listed in the table below
 
 * soapy_source: SoapySDR + drivers for each SDRs (see SoapySDR docs)
@@ -363,7 +363,7 @@ First, please make sure you're running the latest automated build. If your issue
 
 This is a bug in 1.0.0 that was fixed in 1.0.1
 
-In some cases, if a crash happened while the config was being saved, the config file woul be corrupted and SDR++ would refuse to start because of it.
+In some cases, if a crash happened while the config was being saved, the config file would be corrupted and SDR++ would refuse to start because of it.
 
 This has now been fixed. If a config file is corrupted it'll just reset it to its default state.