Docs: Removed condescending language

Author: carolstran

CONTRIBUTING.md

@@ -121,7 +121,7 @@ All of our releases are automated using [semantic-release](https://github.com/se
 
 ## GitHub Apps
 
-We use several GitHub apps to help maintain this repository. While we would like to address every issue and while we would like to be on hand to support every person, unmock is pretty much entirely volunteer run, and we simply don't have the time to do everything. Please don't be offended if an automated app posts in your issue! We're doing what we can with with we have.
+We use several GitHub apps to help maintain this repository. While we would like to address every issue and while we would like to be on hand to support every person, unmock is pretty much entirely volunteer run, and we don't have the time to do everything. Please don't be offended if an automated app posts in your issue! We're doing what we can with with we have.
 
 Currently, we use the [Stale](https://github.com/apps/stale) and [Lock](https://github.com/apps/lock) apps to mark old issues as stale, and to lock issues which have been closed to stop drive-by comments. You can see the configuration files for these in [.github/](.github).
 
@@ -137,7 +137,7 @@ Here are some things you can do today to actively show the unmock team that you'
 - **Review PRs.** We have a lot of open PRs! Some of these are probably ready to merge, and some of them probably need more work. Any extra eyes on PRs are encouraged. Comment on code patterns you think need work, suggest extra tests, and let us know if a PR 'LGTM' ("looks good to me"). The more reviewers we have, the faster we can merge issues, the better this project becomes.
 - **Help out!** If someone files a bug and no one has responded yet, see if you can resolve it! Suggest PRs, or file them yourself. While most contributors are going to only be interested in their own bugs, great maintainers help out with other people's bugs. This is one of the best ways to become an expert at unmock (and Node.js, JavaScript, or pretty much any project) - helping others.
 - **Write docs.** Are our docs missing something important? Are they not clear? Could they be better? Open a PR!
-- **Suggest examples.** Right now, we have a few examples, but we could always have more. Submit small example files and tutorials. At some point, we'll have to work on a better way to display these - for now, it's great to show others how to solve difficult mocking problems easily with unmock.
+- **Suggest examples.** Right now, we have a few examples, but we could always have more. Submit small example files and tutorials. At some point, we'll have to work on a better way to display these - for now, it's great to show others how to solve difficult mocking problems with unmock.
 - **Refactor.** This is one of the hardest things to do, but one of the most useful. Go through the code, and find examples where it could be written better - with better variable names, more useful abstractions, and more elegant patterns. Taking away ten lines of code that are unnecessary is more valuable than submitting a hundred new lines, sometimes. Open a PR or a comment and defend your position; ask for feedback.
 
 Once you've been around for a bit, ask a current Maintainer - one of [the team members](https://github.com/orgs/unmock/people) - whether you can be elevated to Maintainer status and given permissions to close issues and merge PRs. We're interested in how well you know what unmock is about, and how involved you are in the community - not where you're from, how good your English is, or whether or not you can pass a whiteboard test blindfolded. If you think that you've been helpful, let us know. We're friendly, promise. :)

README.md

@@ -36,7 +36,7 @@ $ npm install --save-dev unmock
 
 This README contains all the essential information about unmock. For more examples an in-depth explanations, see the [documentation](https://unmock.io/docs/introduction).
 
-Here is a simple mock, a simple function, and a simple test in jest.
+Here is a mock, a function, and a test in jest.
 
 ```js
 const unmock = require("unmock");
@@ -363,7 +363,7 @@ test("my API always works as expected", runner(async () => {
 
 ## OpenAPI
 
-Unmock supports the reading of OpenAPI specifications out of the box. Simply place your specification in a folder at the root of your project called `__unmock__/<myspecname>`, where `<myspecname>` is the name of the spec on the `unmock.on().services` object.  Several examples of this exist on the internet, most notably [here](https://github.com/unmock/unmock-examples/tree/master/using-service-repository).
+Unmock supports the reading of OpenAPI specifications out of the box. Place your specification in a folder at the root of your project called `__unmock__/<myspecname>`, where `<myspecname>` is the name of the spec on the `unmock.on().services` object.  Several examples of this exist on the internet, most notably [here](https://github.com/unmock/unmock-examples/tree/master/using-service-repository).
 
 ## Tutorials
 

packages/unmock-core/src/__tests__/backend/state.test.ts

@@ -165,7 +165,7 @@ describe("Node.js interceptor", () => {
       expect(response.data).toBe("petstore.swagger.io");
     });
 
-    // this is just a no-op in the new version
+    // this is a no-op in the new version
     test("fails setting an array size for non-array elements", async () => {
       petstore.state(
         withCodes(200),

packages/unmock-core/src/generator.ts

@@ -669,7 +669,7 @@ const toSchema = toSchemas.composeLens(valueLens());
  * - there is at most one path item in the schema
  * - there is at most one operation in the path item
  * It will still work if this is not the case, but it will
- * just pick a random schema, path item and operation, which
+ * pick a random schema, path item and operation, which
  * will lead to nonsensical results.
  * @param schemaRecord the Record<string, OpenAPISchema> that we
  *   are getting the operation from.

packages/unmock-core/src/service/serviceStore.ts

@@ -47,7 +47,7 @@ export class ServiceStore {
       this.cores[hostName] !== undefined &&
       this.cores[serviceName] === undefined
     ) {
-      // remove old service core and wrapper if a service is just renamed
+      // remove old service core and wrapper if a service is renamed
       delete this.cores[hostName];
       delete this.services[hostName];
     }