Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Correct some typos #2172

Merged
merged 1 commit into from
Apr 29, 2021
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ The named `makeServer` function export gives you a lower-level way to hook
Typically, the `/mirage/config.js` file contains a single default export which
is a function defining all your Mirage route handlers. Ember CLI Mirage then
uses this function, along with all the other modules you've defined in
`mirage/models`, `mirage/fixtures`, mirage/factories`, and
`mirage/models`, `mirage/fixtures`, `mirage/factories`, and
`mirage/serializers`, to create your Mirage JS server when your app boots up
in development and testing.

Expand Down Expand Up @@ -49,8 +49,8 @@ The named `makeServer` function export gives you a lower-level way to hook
that this gives you the added benefit of being able to upgrade `miragejs`
independently of `ember-cli-mirage`.

Eventually, `ember-cli-mirage` will shed its re-exports of everythign from
`miragejs', and become a small wrapper library delegating the rest of the work
Eventually, `ember-cli-mirage` will shed its re-exports of everything from
`miragejs`, and become a small wrapper library delegating the rest of the work
to `miragejs`. This will help align the Ember Mirage users with the rest of
the Mirage JS community.
```javascript
Expand Down