spelling: Fix *.md and *.cmd issues.

Signed-off-by: Mario Trangoni <mjtrangoni@gmail.com>

RELEASE_NOTES.md

@@ -524,7 +524,7 @@ Changes
 - Added new C++ abstraction class CivetServer
 - Added thread safety for and fixed websocket defects (Morgan McGuire)
 - Created PKGBUILD to use Arch distribution (Daniel Oaks)
-- Created new documentation on Embeddeding, Building and yaSSL (see docs/).
+- Created new documentation on Embedding, Building and yaSSL (see docs/).
 - Updated License file to include all licenses.
 - Replaced MD5 implementation due to questionable license.
      + This requires new source file md5.inl
@@ -547,7 +547,7 @@ Known Issues
 - Build support for VS6 and some other has been deprecated.
     + This does not impact embedded programs, just the stand-alone build.
     + The old Makefile was renamed to Makefile.deprecated.
-    + This is partcially do to lack fo testing.
+    + This is partcially do to lack of testing.
     + Need to find out what is actually in demand.
 - Build changes may impact current users.
     + As with any change of this type, changes may impact some users.

SECURITY.md

@@ -13,7 +13,7 @@ Selected, critical defects are fixed in the latest release as well.
 
 Note that different security policies apply to different files/folders in this project:
 - The core components are include/civetweb.h, src/civetweb.c and src/*.inl.  These files are part of every server instance in production. Therefore they have to undergo the most intensive security tests and reviews.
-- The src/main.c file is used by the standalone server. It is used in various tests in combination with the aforementioned core components. Aplications embedding civetweb will not use main.c and, thus, do not suffer from any vulnerabilities therein.
+- The src/main.c file is used by the standalone server. It is used in various tests in combination with the aforementioned core components. Applications embedding civetweb will not use main.c and, thus, do not suffer from any vulnerabilities therein.
 - The example folders contain different usage examples in different maintenance state. This is explained in detail in the README file there.
 - The content of all test folders (test, unittest, fuzztest) is used to test the server functionality. These tests are not designed with security in mind - on the contrary, some tests contain scripts or settings that even introduce security leaks on purpose. All tests are only meant to be run in a test environment. You should not use the content of any test folder in production. Also certificates in "resources/cert" are only meant to be used in test environments and must never be used in production.
 

build.cmd

@@ -124,7 +124,7 @@
              build ^
              install
 @for %%m in (%methods%) do @(
-  call :log 3 "Excuting the '%%m' method"
+  call :log 3 "Executing the '%%m' method"
   call :log 8
   call :%%~m
   if errorlevel 1 (
@@ -400,9 +400,9 @@
 @endlocal & set "%var%=%file_path%"
 @goto :eof
 
-:administrator_check - Checks for administrator priviledges
+:administrator_check - Checks for administrator privileges
 @setlocal
-@call :log 2 "Checking for administrator priviledges"
+@call :log 2 "Checking for administrator privileges"
 @set "key=HKLM\Software\VCA\Tool Chain\Admin Check"
 @reg add "%key%" /v Elevated /t REG_DWORD /d 1 /f > nul 2>&1
 @if errorlevel 1 exit /b 1