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

platform/docs/versioned_docs/version-2.0-deprecated/deployment/index.md

@@ -99,7 +99,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](./../configuring/index.md).
 
 #### What if I don't have an imaging archive?
@@ -273,7 +273,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.
 

platform/docs/versioned_docs/version-2.0-deprecated/deployment/recipes/build-for-production.md

@@ -75,7 +75,7 @@ directory. Our build process knows which configuration file to use based on the
 and registered extension's features, are configured using this file.
 
 The easiest way to apply your own configuration is to modify the `default.js`
-file. For more advanced cofiguration options, check out our
+file. For more advanced configuration options, check out our
 [configuration essentials guide](/configuring/index.md).
 
 ## Next Steps

platform/docs/versioned_docs/version-2.0-deprecated/deployment/recipes/nginx--image-archive.md

@@ -8,7 +8,7 @@ sidebar_position: 4
 
 At a certain point, you may want others to have access to your instance of the
 OHIF Viewer and its medical imaging data. This post covers one of many potential
-setups that accomplish that. Please note, noticably absent is user account
+setups that accomplish that. Please note, noticeably absent is user account
 control.
 
 Do not use this recipe to host sensitive medical data on the open web. Depending
@@ -21,12 +21,12 @@ that builds on the lessons learned here.
 
 Our two biggest hurdles when hosting our image archive and web client are:
 
-- Risks related to exposing our PACS to the netowrk
+- Risks related to exposing our PACS to the network
 - Cross-Origin Resource Sharing (CORS) requests
 
 ### Handling Web Requests
 
-We mittigate our first issue by allowing [Nginx][nginx] to handle incoming web
+We mitigate our first issue by allowing [Nginx][nginx] to handle incoming web
 requests. Nginx is open source software for web serving, reverse proxying,
 caching, and more. It's designed for maximum performance and stability --
 allowing us to more reliably serve content than Orthanc's built-in server can.

platform/docs/versioned_docs/version-2.0-deprecated/deployment/recipes/static-assets.md

@@ -16,7 +16,7 @@ less product offerings.
 While not required, it can simplify things to host your Web Viewer alongside
 your image archive. Services with more robust product offerings, like
 `Google Cloud`, `Microsoft's Azure`, and `Amazon Web Services (AWS)`, are able
-to accomodate this setup.
+to accommodate this setup.
 
 _Drag-n-drop_
 

platform/docs/versioned_docs/version-2.0-deprecated/deployment/recipes/user-account-control.md

@@ -77,7 +77,7 @@ _Create Your First User_
   - Email Verified: `ON`
   - Click `Save`
 - Click the `Credentials` Tab
-  - New Pasword: `test`
+  - New Password: `test`
   - Password Confirmation: `test`
   - Temporary: `OFF`
   - Click: `Reset Password`