docs(spelling): Add codespell config + github action, run and fix a good number of typos (#3645)

platform/docs/docs/deployment/docker.md

@@ -239,7 +239,7 @@ To create a self-signed certificate:
     |Country Name (2 letter code) [AU]|
     |State or Province Name (full name) [Some-State]|
     |Locality Name (eg, city) []|
-    |Organization Name (eg, company) [Internet Widgits Pty Ltd]|
+    |Organization Name (eg, company) [Internet Widgets Pty Ltd]|
     |Organizational Unit Name (eg, section) []|
     |Common Name (e.g. server FQDN or YOUR name) []|
     |Email Address []|

platform/docs/docs/deployment/index.md

@@ -93,7 +93,7 @@ support it yet, but it is gaining wider adoption.
 
 If you have an existing archive and intend to host the OHIF Viewer at the same
 domain name as your archive, then connecting the two is as simple as following
-the steps layed out in our
+the steps laid out in our
 [Configuration Essentials Guide](./../configuration/configurationFiles.md).
 
 #### What if I don't have an imaging archive?
@@ -297,7 +297,7 @@ You can find an example of this setup in our
 
 In general, we recommend using the "Authorization Code Flow" ( [see
 `response_type=code` here][code-flows]); however, the "Implicit Flow" ( [see
-`response_type=token` here][code-flows]) can work if additonal precautions are
+`response_type=token` here][code-flows]) can work if additional precautions are
 taken. If the flow you've chosen produces a JWT Token, it's validity can be used
 to secure access to your Image Archive as well.