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

platform/docs/versioned_docs/version-1.0-deprecated/essentials/meteor-packages.md

@@ -54,7 +54,7 @@ This package also stores Meteor components for the interactive lesion table used
 ### User (*ohif-user*)
 
 ### Basic Viewer Components (*ohif-viewerbase*)
-This is the largest package in the repository. It holds a large number of re-usable Meteor components that are used to build both the OHIF Viewer and Lesion Tracker.
+This is the largest package in the repository. It holds a large number of reusable Meteor components that are used to build both the OHIF Viewer and Lesion Tracker.
 
 ### WADO Proxy (*ohif-wadoproxy*)
 Proxy for CORS

platform/docs/versioned_docs/version-1.0-deprecated/faq/technical.md

@@ -5,4 +5,4 @@ At the time of project conception, Meteor was a simple way to begin using bleedi
 
 ## Do you have any plans to stop using Meteor?
 
-We have considered migrating templates from Blaze (http://blazejs.org/) to React (https://reactjs.org/) or Vue (https://vuejs.org/), simply because these decouple the view layer from the remainder of the application. Blaze currently lacks [Stand-alone Support](http://blazejs.org/#Better-Stand-alone-Support) which means that our templates are not re-usable outside of a Meteor application. This is certainly a downside, but the resource cost to migrate every template is significant.
+We have considered migrating templates from Blaze (http://blazejs.org/) to React (https://reactjs.org/) or Vue (https://vuejs.org/), simply because these decouple the view layer from the remainder of the application. Blaze currently lacks [Stand-alone Support](http://blazejs.org/#Better-Stand-alone-Support) which means that our templates are not reusable outside of a Meteor application. This is certainly a downside, but the resource cost to migrate every template is significant.