Merge branch 'develop' of https://github.com/stdlib-js/stdlib into develop

Author: kgryte

CONTRIBUTING.md

@@ -61,7 +61,7 @@ When filing an [issue][stdlib-issues], provide the following, where possible:
 -   The expected results.
 -   List of affected environments (e.g., browser, browser version, `npm` version, Node.js version, operating system, and stdlib version).
 
-When pasting code blocks or output, use triple backticks to enable proper formatting. Surround inline code with single backticks. For other Markdown formatting tips and trips, see GitHub's [Markdown guide][github-markdown-guide].
+When pasting code blocks or output, use triple backticks to enable proper formatting. Surround inline code with single backticks. For other Markdown formatting tips and tricks, see GitHub's [Markdown guide][github-markdown-guide].
 
 Be aware that the `@` symbol tags users on GitHub, so **always** surround package names with backticks (e.g., `@stdlib/utils/copy`).
 
@@ -87,7 +87,7 @@ If you have found a bug that you would like to fix,
 
 If you want to contribute a new feature or a breaking change to stdlib, be sure to
 
--   consult the [Gitter][stdlib-gitter] channel to discuss ideas and to gather feedback as to whether a feature would be better developed as an external package. Discussing the design upfront helps ensure that we're ready to accept to your work.
+-   consult the [Gitter][stdlib-gitter] channel to discuss ideas and to gather feedback as to whether a feature would be better developed as an external package. Discussing the design upfront helps ensure that we're ready to accept your work.
 -   write an RFC (request for comments) detailing the proposed change and submit as an issue on the project GitHub issue tracker.
 -   wait for RFC approval.
 -   submit a [pull request][stdlib-pull-requests], making sure to adhere to the guidance set forth in the RFC.

GOVERNANCE.md

@@ -48,7 +48,7 @@ New Core Contributors can be nominated by any existing Core Contributors. Once t
 
 The TSC can remove inactive Core Contributors or provide them with _emeritus_ status. Emeriti may request that the TSC restore them to active status.
 
-A Core Contributor is automatically made emeritus (and removed from active Core Contributor status) if more than 18 months has passed since the Core Contributor authored or approved a Pull Request that has landed.
+A Core Contributor is automatically made emeritus (and removed from active Core Contributor status) if more than 18 months have passed since the Core Contributor authored or approved a Pull Request that has landed.
 
 ##### Core Contributor Activities
 
@@ -150,7 +150,7 @@ Substantial portions of this document were adapted from the following governance
 
 -   [NumPy][numpy-governance]
 -   [Node.js][nodejs-governance]
--   [Sckit-learn][scikit-learn-governance]
+-   [Scikit-learn][scikit-learn-governance]
 
 ## License
 

README.md

@@ -162,7 +162,7 @@ Thank you for being a part of our community! Your support is invaluable to us!
 
 To accommodate various use cases, stdlib can be used in multiple ways. The preferred method of use depends on your individual use case. We've provided some user stories to help you identify the best approach. 😃
 
-While this project's installation instructions defaults to using [npm][npm] for package management, installation via other package managers, such as [yarn][yarn], should be a matter of simply swapping out [npm][npm] commands with those of the relevant package manager.
+While this project's installation instructions default to using [npm][npm] for package management, installation via other package managers, such as [yarn][yarn], should be a matter of simply swapping out [npm][npm] commands with those of the relevant package manager.
 
 ### User Stories
 

SECURITY.md

@@ -107,7 +107,7 @@ Our disclosure policy is as follows:
 
 -   Depending on the outcome of validation, the primary handler will communicate to the individual who submitted the potential vulnerability one of the following possible responses:
 
-    -   **Acceptance**: what was reported is a considered a new vulnerability.
+    -   **Acceptance**: what was reported is considered a new vulnerability.
     -   **Rejection**: what was reported is not considered a new vulnerability.
     -   **Needs more information**: we need more information in order to evaluate what was reported.