diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 960213c37073..638e1aade6f2 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -175,7 +175,7 @@ So the way our script works is that it:
 Our script leaves the local registry running, for **as long as you keep it running** you can install storybook packages from this local registry.
 
 - Navigate to your own project and then change `package.json` so the storybook packages match the version of the one you just published.
-- Then just do the normal install procedure using `yarn` or `npm`
+- Then you can install using `yarn` or `npm`
 - Start using your storybook as normally.
 
 If you've made a change to storybook's codebase and would want this change to be reflected in your app:
@@ -229,7 +229,7 @@ We use the following label scheme to categorize issues:
 
 All issues should have a `type` label. `bug`/`feature`/`question`/`discussion` are self-explanatory. `dependencies` is for keeping package dependencies up to date. `maintenance` is a catch-all for any kind of cleanup or refactoring.
 
-They should also have one or more `area`/`status` labels. We use these labels to filter issues down so we can easily see all of the issues for a particular area, and keep the total number of open issues under control.
+They should also have one or more `area`/`status` labels. We use these labels to filter issues down so we can see all of the issues for a particular area, and keep the total number of open issues under control.
 
 For example, here is the list of [open, untyped issues](https://github.com/storybookjs/storybook/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20-label%3A%22bug%22%20-label%3A%22discussion%22%20-label%3A%22feature%22%20-label%3A%22maintenance%22%20-label%3A%22question%20%2F%20support%22%20-label%3A%22documentation%22%20-label%3A%22greenkeeper%22), or here is a list of [bugs that have not been modified since 2017-04-01](https://github.com/storybookjs/storybook/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aopen%20label%3A%22bug%22%20updated%3A%3C%3D2017-04-01%20). For more info see [searching issues](https://help.github.com/articles/searching-issues/) in the Github docs.
 
diff --git a/MIGRATION.md b/MIGRATION.md
index cdfdb289a85c..ada5ec601e25 100644
--- a/MIGRATION.md
+++ b/MIGRATION.md
@@ -655,7 +655,7 @@ Storybook now uses Babel 7. There's a couple of cases when it can break with you
 If you are using `create-react-app` (aka CRA), you may need to do some manual steps to upgrade, depending on the setup.
 
 - `create-react-app@1` may require manual migrations.
-  - If you're adding storybook for the first time, it should just work: `sb init` should add the correct dependencies.
+  - If you're adding storybook for the first time: `sb init` should add the correct dependencies.
   - If you're upgrading an existing project, your `package.json` probably already uses Babel 6, making it incompatible with `@storybook/react@4` which uses Babel 7. There are two ways to make it compatible, each of which is spelled out in detail in the next section:
     - Upgrade to Babel 7 if you are not dependent on Babel 6-specific features.
     - Migrate Babel 6 if you're heavily dependent on some Babel 6-specific features).
@@ -748,7 +748,7 @@ This was done to support different major versions of babel.
 
 ### Base webpack config now contains vital plugins ([#1775](https://github.com/storybookjs/storybook/pull/1775))
 
-This affects you if you use custom webpack config in [Full Control Mode](https://storybook.js.org/configurations/custom-webpack-config/#full-control-mode) while not preserving the plugins from `storybookBaseConfig`. Before `3.3`, preserving them was just a recommendation, but now it [became](https://github.com/storybookjs/storybook/pull/2578) a requirement.
+This affects you if you use custom webpack config in [Full Control Mode](https://storybook.js.org/configurations/custom-webpack-config/#full-control-mode) while not preserving the plugins from `storybookBaseConfig`. Before `3.3`, preserving them was a recommendation, but now it [became](https://github.com/storybookjs/storybook/pull/2578) a requirement.
 
 ### Refactored Knobs
 
@@ -879,7 +879,7 @@ The new package names are:
 | `@kadira/storybook-addon-graphql`            | `@storybook/addon-graphql`       |
 | `@kadira/react-storybook-decorator-centered` | `@storybook/addon-centered`      |
 
-If your codebase is small, it's probably doable to just replace them by hand. (in your codebase and in `package.json`).
+If your codebase is small, it's probably doable to replace them by hand (in your codebase and in `package.json`).
 
 But if you have a lot of occurrences in your codebase, you can use a [codemod we created](./lib/codemod) for you.
 
diff --git a/ROADMAP.md b/ROADMAP.md
index f98687178543..82f11931ff23 100644
--- a/ROADMAP.md
+++ b/ROADMAP.md
@@ -24,7 +24,7 @@ Doing these will be backwards compatible.
 
 ### Responsive + multi-device viewports preview.
 
-If you're smart about it you can already view the preview on multiple devices and windows. It's just an iframe after-all.
+If you're smart about it you can already view the preview on multiple devices and windows. It's an iframe after-all.
 But story selection and addon-settings are not synced.
 We want to make this much much simpler and a core feature of storybook.
 
diff --git a/addons/contexts/README.md b/addons/contexts/README.md
index 3362dfa6fdff..c781dacbe0e9 100644
--- a/addons/contexts/README.md
+++ b/addons/contexts/README.md
@@ -25,7 +25,7 @@ once then apply it everywhere**.
 
 1. Define a single global file for managing contextual environments (a.k.a. containers) for all of your stories
    declaratively. No more repetitive setups or noisy wrapping, making your stories more focused and readable.
-2. Support dynamic contextual props switching from Storybook toolbar at runtime. You can easily slice into
+2. Support dynamic contextual props switching from Storybook toolbar at runtime. You can slice into
    different environments (e.g. languages or themes ) to understand how your component is going to respond.
 3. Library agnostic: no presumption on what kind of components you want to wrap around your stories. You can even
    use it to bridge with your favorite routing, state-management solutions, or even your own
@@ -65,7 +65,7 @@ import { contexts } from './configs/contexts'; // we will define the contextual
 addDecorator(withContexts(contexts));
 ```
 
-Alternatively, just like other addons, you can use this addon only for a given set of stories:
+Alternatively, like other addons, you can use this addon only for a given set of stories:
 
 ```js
 import { storiesOf } from '@storybook/[framework]';
@@ -220,7 +220,7 @@ be shown at first in the toolbar menu in your Storybook.
 
 ## 📔 Notes
 
-1. You can use this addon to inject any valid components, that is why `icon` and `params` can be just optional.
+1. You can use this addon to inject any valid components, that is why `icon` and `params` can be optional.
 2. As mentioned, extra contextual environment setups can be added at the story level. Please make sure they are
    passed via the second argument as `{ contexts: [{ /* extra contexts */ }}`.
 3. Additional `params` can be "appended" into an existing setup at the story level too (make sure it goes with the
diff --git a/addons/docs/docs/docspage.md b/addons/docs/docs/docspage.md
index 900f6d6c48f9..4b5bf43f9086 100644
--- a/addons/docs/docs/docspage.md
+++ b/addons/docs/docs/docspage.md
@@ -241,7 +241,7 @@ The docs preset assumes this naming convention for its `source-loader` setup. If
 
 Due to the complex nature of writing a cross-framework utility like Storybook, the story blocks for most frameworks exist within an `<iframe>` element. This creates a clean separation of the context the code for each framework lives inside, but, of course, it isn't a perfect tradeoff. It does create a set of disadvantages--namely, you have to explicitly set the height of a story. It also causes some headaches for certain dev tools (Vue dev tools, for example, don't pick up components that exist in an iframe, without substantial jerry-rigging).
 
-That being said, there is a system in place to remove the necessity of this tradeoff. The docs configuration contains two options, `inlineStories` and `prepareForInline` that can work together to integrate non-react stories seamlessly (or should I say "scroll-bar-less-ly") into DocsPage. Setting `inlineStories` to `true` is the easy part. It's just tells storybook to stop putting your stories into an iframe. The hard(er) part is providing the `prepareForInline` parameter. This parameter accepts a function that transforms story content in your given framework into something react can render. Any given framework will need to approach this in a different way. Angular, for example, might convert its story content into a custom element (you can read about that [here](https://angular.io/guide/elements)). We've actually taken the initiative and implemented Vue inline stories _for you_ in the default docs config for Vue, because we're such nice people. The following docs config block allows Vue components to be rendered inline through a simple effect hook provided by [@egoist/vue-to-react](https://github.com/egoist/vue-to-react):
+That being said, there is a system in place to remove the necessity of this tradeoff. The docs configuration contains two options, `inlineStories` and `prepareForInline` that can work together to integrate non-react stories seamlessly (or should I say "scroll-bar-less-ly") into DocsPage. Setting `inlineStories` to `true` is the easy part. It tells storybook to stop putting your stories into an iframe. The hard(er) part is providing the `prepareForInline` parameter. This parameter accepts a function that transforms story content in your given framework into something react can render. Any given framework will need to approach this in a different way. Angular, for example, might convert its story content into a custom element (you can read about that [here](https://angular.io/guide/elements)). We've actually taken the initiative and implemented Vue inline stories _for you_ in the default docs config for Vue, because we're such nice people. The following docs config block allows Vue components to be rendered inline through a simple effect hook provided by [@egoist/vue-to-react](https://github.com/egoist/vue-to-react):
 
 ```js
 import React from 'react';
diff --git a/addons/docs/docs/faq.md b/addons/docs/docs/faq.md
index c64e62fe1d72..871d80643a01 100644
--- a/addons/docs/docs/faq.md
+++ b/addons/docs/docs/faq.md
@@ -40,7 +40,7 @@ Shows up in the dev tools as follows:
   <img src="./media/faq-devtools.png" width="100%" />
 </center>
 
-This is just [Component Story Format (CSF)](https://medium.com/storybookjs/component-story-format-66f4c32366df), so it should be easy to debug. You can copy and paste this code into a new `.stories.js` file and play around with it at a lower level to understand what's going wrong.
+This is [Component Story Format (CSF)](https://medium.com/storybookjs/component-story-format-66f4c32366df), so there are ways to debug. You can copy and paste this code into a new `.stories.js` file and play around with it at a lower level to understand what's going wrong.
 
 ## More resources
 
diff --git a/addons/docs/docs/mdx.md b/addons/docs/docs/mdx.md
index 25e6e359cf21..95d114c2e9aa 100644
--- a/addons/docs/docs/mdx.md
+++ b/addons/docs/docs/mdx.md
@@ -74,7 +74,7 @@ export const allCheckboxes = () => (
 );
 ```
 
-There's a one-to-one mapping from the code in `MDX` to `CSF`, which in turn directly corresponds to Storybook's internal `storiesOf` API. As a user this means your existing Storybook knowledge should easily translate between the three. And technically, this means that the transformations that happen under the hood are simple and predictable.
+There's a one-to-one mapping from the code in `MDX` to `CSF`, which in turn directly corresponds to Storybook's internal `storiesOf` API. As a user, this means your existing Storybook knowledge should translate between the three. And technically, this means that the transformations that happen under the hood are simple and predictable.
 
 ## Writing stories
 
diff --git a/addons/docs/docs/recipes.md b/addons/docs/docs/recipes.md
index 4a9659a5158d..8840c0afe212 100644
--- a/addons/docs/docs/recipes.md
+++ b/addons/docs/docs/recipes.md
@@ -171,9 +171,9 @@ addParameters({
 
 > ⚠️ The `--docs` flag is an experimental feature in Storybook 5.2. The behavior may change in 5.3 outside of the normal semver rules. Be forewarned!
 
-The Storybook UI is a workshop for developing components in isolation. Storybook Docs is a showcase for documenting your components. During component/docs development, it’s useful to see both of these modes side by side. But when you export your static storybook, you might want to just export the docs to reduce clutter.
+The Storybook UI is a workshop for developing components in isolation. Storybook Docs is a showcase for documenting your components. During component/docs development, it’s useful to see both of these modes side by side. But when you export your static storybook, you might want to export the docs to reduce clutter.
 
-To address this, we’ve added a CLI flag to export just the docs. This flag is also available in dev mode:
+To address this, we’ve added a CLI flag to only export the docs. This flag is also available in dev mode:
 
 ```sh
 yarn build-storybook --docs
diff --git a/addons/jest/README.md b/addons/jest/README.md
index 5670a157f17f..c5845d4a6bc6 100644
--- a/addons/jest/README.md
+++ b/addons/jest/README.md
@@ -38,7 +38,7 @@ You may want to add it the result file to `.gitignore`, since it's a generated f
 
 But much like lockfiles and snapshots checking-in generated files can have certain advantages as well. It's up to you.
 We recommend to **do** check in the test results file so starting storybook from an clean git clone doesn't require running all tests first,
-but this can mean you'll experience merge conflicts on this file in the future. (_re-generating this file is super easy though, just like lockfiles and snapshots_)
+but this can mean you'll experience merge conflicts on this file in the future. (_re-generating this file is very similar to re-generating lockfiles and snapshots_)
 
 ## Generating the test results
 
diff --git a/addons/storyshots/storyshots-core/README.md b/addons/storyshots/storyshots-core/README.md
index 02d0553c2bf1..fc0dc0701c7a 100644
--- a/addons/storyshots/storyshots-core/README.md
+++ b/addons/storyshots/storyshots-core/README.md
@@ -17,7 +17,7 @@ yarn add @storybook/addon-storyshots --dev
 ```
 
 ## Configure your app for Jest
-In many cases, for example Create React App, it's already configured for Jest. You just need to create a filename with the extension `.test.js`.
+In many cases, for example Create React App, it's already configured for Jest. You need to create a filename with the extension `.test.js`.
 
 If you still need to configure jest you can use the resources mentioned below:
 
@@ -602,7 +602,7 @@ module.exports = {
 #### integrityOptions
 
 This option is useful when running test with `multiSnapshotWithOptions(options)` in order to track snapshots are matching the stories. (disabled by default).
-The value is just a [settings](https://github.com/isaacs/node-glob#options) to a `glob` object, that searches for the snapshot files.
+The value is a [settings](https://github.com/isaacs/node-glob#options) to a `glob` object, that searches for the snapshot files.
 
 ```js
 initStoryshots({
diff --git a/addons/storyshots/storyshots-core/stories/storyshot.async.test.js b/addons/storyshots/storyshots-core/stories/storyshot.async.test.js
index eb80b195496a..6075c381b928 100644
--- a/addons/storyshots/storyshots-core/stories/storyshot.async.test.js
+++ b/addons/storyshots/storyshots-core/stories/storyshot.async.test.js
@@ -40,7 +40,7 @@ initStoryshots({
         done();
       }, TIMEOUT);
     } else {
-      // If not async just mark the test as done
+      // If not async, mark the test as done
       done();
     }
   },
diff --git a/app/react-native/docs/manual-setup.md b/app/react-native/docs/manual-setup.md
index 5b098217bc6a..4fb5be1480c7 100644
--- a/app/react-native/docs/manual-setup.md
+++ b/app/react-native/docs/manual-setup.md
@@ -78,7 +78,7 @@ import StorybookUI from './storybook';
 export default StorybookUI;
 ```
 
-If you cannot replace your entry point just make sure that the component exported from `./storybook` is displayed
+If you cannot replace your entry point, make sure that the component exported from `./storybook` is displayed
 somewhere in your app. `StorybookUI` is a RN `View` component that can be embedded anywhere in your 
 RN application, e.g. on a tab or within an admin screen.
 
diff --git a/docs/src/new-components/basics/tooltip/Tooltip.stories.js b/docs/src/new-components/basics/tooltip/Tooltip.stories.js
index 9c0bfb7094e7..b891e7a0a2d8 100644
--- a/docs/src/new-components/basics/tooltip/Tooltip.stories.js
+++ b/docs/src/new-components/basics/tooltip/Tooltip.stories.js
@@ -3,7 +3,7 @@ import { storiesOf } from '@storybook/react';
 import styled from 'styled-components';
 import Tooltip from './Tooltip';
 
-// Popper would position the tooltip absolutely. We just need to make sure we are pos:rel
+// Popper would position the tooltip absolutely. We need to make sure we are pos:rel
 const mockPopperProps = { style: { position: 'relative', top: '20px', left: '20px' } };
 
 const Content = styled.div`
diff --git a/docs/src/pages/addons/addon-gallery/index.md b/docs/src/pages/addons/addon-gallery/index.md
index 229204cccba2..db862c8633e1 100644
--- a/docs/src/pages/addons/addon-gallery/index.md
+++ b/docs/src/pages/addons/addon-gallery/index.md
@@ -93,7 +93,7 @@ Break your stories down into smaller categories (chapters) and subcategories (se
 ### [Props Combinations](https://github.com/evgenykochetkov/react-storybook-addon-props-combinations)
 
 Given possible values for each prop, renders your component with all combinations of prop values.
-Useful for finding edge cases or just seeing all component states at once.
+Useful for finding edge cases or seeing all component states at once.
 
 ### [Material-UI](https://github.com/sm-react/storybook-addon-material-ui)
 
diff --git a/docs/src/pages/addons/api/index.md b/docs/src/pages/addons/api/index.md
index 966a722cf5e7..5918dc24726b 100644
--- a/docs/src/pages/addons/api/index.md
+++ b/docs/src/pages/addons/api/index.md
@@ -60,11 +60,11 @@ The render function is called with `active` and `key`.
 
 When the panel is in focus in the UI, the `active` will be true.
 
-As you can see, you can set any React Component as the panel. Currently, it's just a text. But you can do anything you want. You should specify the panel title. It could be a plain text.
+As you can see, you can set any React Component as the panel. Currently, it's one line of text. But you can do anything you want. You should specify the panel title. It could be a plain text.
 
 ## makeDecorator API
 
-The `makeDecorator` API can be used to create decorators in the style of the official addons easily. Use it like so:
+The `makeDecorator` API can be used to create decorators in the style of the official addons. Use it like so:
 
 ```jsx
 import { makeDecorator } from '@storybook/addons';
diff --git a/docs/src/pages/addons/writing-addons/index.md b/docs/src/pages/addons/writing-addons/index.md
index d344ac424462..08cbd3d75bc6 100644
--- a/docs/src/pages/addons/writing-addons/index.md
+++ b/docs/src/pages/addons/writing-addons/index.md
@@ -131,7 +131,7 @@ Now we need to create two files, `register.js` and `index.js,`. `register.js` wi
 
 Let's add the following content to the `index.js`. It will expose a decorator called `withFoo` which we use the `.addDecorator()` API to decorate all our stories.
 
-The `@storybook/addons` package contains a `makeDecorator` function which we can easily use to create such a decorator:
+The `@storybook/addons` package contains a `makeDecorator` function which we can use to create such a decorator:
 
 ```js
 import React from 'react';
@@ -203,7 +203,7 @@ Using the hook, we'll listen for events and gain access to the `emit` function f
 
 It also listens to another event, called onStory, in the storybook API, which fires when the user selects a story.
 
-Multiple addons can be loaded, but only a single panel can be shown, the render function will receive an `active` prop, which is true if the addon is shown. It is up to you to decide if this mean your component must be unmounted, or just visually hidden. This allows you to keep state but unmount expensive renderings.
+Multiple addons can be loaded, but only a single panel can be shown, the render function will receive an `active` prop, which is true if the addon is shown. It is up to you to decide if this mean your component must be unmounted, or visually hidden. This allows you to keep state but unmount expensive renderings.
 
 The `AddonPanel` component will stop rendering of it's children if it's `active`-prop is false.
 
@@ -221,7 +221,7 @@ export const Panel = () => {
 }
 ```
 
-This will store your addon's state into storybook core state, and so when your component gets unmounted & remounted, the state will just be restored.
+This will store your addon's state into storybook core state, and so when your component gets unmounted & remounted, the state will be restored.
 
 This is also a great way to sync state between multiple components of the same addon.
 
@@ -295,7 +295,7 @@ You can learn more about the complete API [here](/addons/api).
 
 ## Packaging
 
-You can package this addon into a NPM module very easily. As an example, have a look at this [package](https://github.com/storybookjs/storybook/tree/master/addons/notes).
+It's possible to package this addon into a NPM module. As an example, have a look at this [package](https://github.com/storybookjs/storybook/tree/master/addons/notes).
 
 In addition to moving the above code to a NPM module, we've set `react` and `@storybook/addons` as peer dependencies.
 
diff --git a/docs/src/pages/basics/faq/index.md b/docs/src/pages/basics/faq/index.md
index 0192f72ed9d0..7b7020393443 100644
--- a/docs/src/pages/basics/faq/index.md
+++ b/docs/src/pages/basics/faq/index.md
@@ -22,7 +22,7 @@ Next automatically defines `React` for all of your files via a babel plugin. You
 
 ### How do I setup Storybook to share Webpack configuration with Next.js?
 
-You can generally reuse webpack rules fairly easily by placing them in a file that is `require()`-ed from both your `next.config.js` and your `.storybook/webpack.config.js` files. For example, [this gist](https://gist.github.com/metasean/cadd2becd60cc3b295bf49895a56f9b4) sets both next.js and storybook up with global stylesheets.
+You can generally reuse webpack rules by placing them in a file that is `require()`-ed from both your `next.config.js` and your `.storybook/webpack.config.js` files. For example, [this gist](https://gist.github.com/metasean/cadd2becd60cc3b295bf49895a56f9b4) sets both next.js and storybook up with global stylesheets.
 
 ### Why is there no addons channel?
 
diff --git a/docs/src/pages/basics/writing-stories/index.md b/docs/src/pages/basics/writing-stories/index.md
index c48b68e064c6..99f1e2df46bf 100644
--- a/docs/src/pages/basics/writing-stories/index.md
+++ b/docs/src/pages/basics/writing-stories/index.md
@@ -209,9 +209,9 @@ special.story = {
 };
 ```
 
-Decorators are not just for story formatting, they are generally useful for any kind of context needed by a story.
+Decorators are not only for story formatting, they are generally useful for any kind of context needed by a story.
 
-- Theming libraries require a theme to be passed in through context. Rather than redefining this in every story, just add a decorator.
+- Theming libraries require a theme to be passed in through context. Rather than redefining this in every story, add a decorator.
 - Likewise, state management libraries like Redux provide a global data store through context.
 - Finally, Storybook [addons](../../addons/introduction) heavily use decorators. For example, the Storybook's [Knobs addon](https://github.com/storybookjs/storybook/tree/next/addons/knobs) uses decorators to modify the input properties of the story based on a UI.
 
diff --git a/docs/src/pages/configurations/default-config/index.md b/docs/src/pages/configurations/default-config/index.md
index 27cb53439df5..7e87b7dc63ca 100644
--- a/docs/src/pages/configurations/default-config/index.md
+++ b/docs/src/pages/configurations/default-config/index.md
@@ -189,7 +189,7 @@ import './styles.css';
 ### Image and Static File Support
 
 You can also import images and media files directly via JavaScript.
-This helps you to write stories with media files easily. This is how to do it:
+This helps you to write stories with media files. This is how to do it:
 
 ```js
 import React from 'react';
diff --git a/docs/src/pages/configurations/serving-static-files/index.md b/docs/src/pages/configurations/serving-static-files/index.md
index 7c3d47cdb17a..9cf869e32ad1 100644
--- a/docs/src/pages/configurations/serving-static-files/index.md
+++ b/docs/src/pages/configurations/serving-static-files/index.md
@@ -71,7 +71,7 @@ storiesOf('<img />', module)
 
 ## 3. Via a CDN
 
-Upload your files to an online CDN and just reference them.
+Upload your files to an online CDN and reference them.
 In this example we're using a placeholder image service.
 
 ```js
diff --git a/docs/src/pages/configurations/theming/index.md b/docs/src/pages/configurations/theming/index.md
index 70be2f547889..99c6ee376f43 100644
--- a/docs/src/pages/configurations/theming/index.md
+++ b/docs/src/pages/configurations/theming/index.md
@@ -3,7 +3,7 @@ id: 'theming'
 title: 'Theming Storybook'
 ---
 
-Storybook is theme-able! Just set a `theme` in the [options parameter](../options-parameter)!
+Storybook is theme-able! Set a `theme` in the [options parameter](../options-parameter)!
 
 ## Global theming
 
diff --git a/docs/src/pages/configurations/typescript-config/index.md b/docs/src/pages/configurations/typescript-config/index.md
index 31146ee143b0..a36e6f283bef 100644
--- a/docs/src/pages/configurations/typescript-config/index.md
+++ b/docs/src/pages/configurations/typescript-config/index.md
@@ -16,7 +16,7 @@ yarn add -D @storybook/addon-info react-docgen-typescript-loader # optional but
 yarn add -D jest "@types/jest" ts-jest #testing
 ```
 
-We have had the best experience using `awesome-typescript-loader`, but other tutorials may use `ts-loader`, just configure accordingly. You can even use `babel-loader` with a `ts-loader` configuration.
+We have had the best experience using `awesome-typescript-loader`, but other tutorials may use `ts-loader`, so be sure to configure accordingly. You can even use `babel-loader` with a `ts-loader` configuration.
 
 ### Setting up TypeScript to work with Storybook
 
@@ -75,7 +75,7 @@ The above example shows a working Webpack config with the [TSDocgen plugin](http
 }
 ```
 
-This is for the default configuration where `/stories` is a peer of `src`. If you have them all in just `src` you may wish to replace `"rootDirs": ["src", "stories"]` above with `"rootDir": "src",`.
+This is for the default configuration where `/stories` is a peer of `src`. If you have them all in `src`, you may wish to replace `"rootDirs": ["src", "stories"]` above with `"rootDir": "src",`.
 
 ## Setting up TypeScript with babel-loader
 
diff --git a/docs/src/pages/formats/component-story-format/index.md b/docs/src/pages/formats/component-story-format/index.md
index fa094eb8cfcd..855fa2d5307b 100644
--- a/docs/src/pages/formats/component-story-format/index.md
+++ b/docs/src/pages/formats/component-story-format/index.md
@@ -65,7 +65,7 @@ it('should format CSF exports with sensible defaults', () => {
 });
 ```
 
-When you want to change the name of your story, just rename the CSF export. This will change the name of the story and also change the Story's ID / URL.
+When you want to change the name of your story, rename the CSF export. This will change the name of the story and also change the Story's ID / URL.
 
 You should use the `story.name` option in the following cases:
 
diff --git a/docs/src/pages/guides/guide-react-native/index.md b/docs/src/pages/guides/guide-react-native/index.md
index 128504c84b5b..6fd2baf3c1a1 100644
--- a/docs/src/pages/guides/guide-react-native/index.md
+++ b/docs/src/pages/guides/guide-react-native/index.md
@@ -78,7 +78,7 @@ The easiest solution is to replace your app entry with:
 export default from './storybook';
 ```
 
-If you cannot replace your entry point just make sure that the component exported from `./storybook` is displayed somewhere in your app. `StorybookUI` is a RN `View` component that can be embedded anywhere in your RN application, e.g. on a tab or within an admin screen.
+If you cannot replace your entry point, make sure that the component exported from `./storybook` is displayed somewhere in your app. `StorybookUI` is a RN `View` component that can be embedded anywhere in your RN application, e.g. on a tab or within an admin screen.
 
 ---
 
diff --git a/docs/src/pages/guides/guide-riot/index.md b/docs/src/pages/guides/guide-riot/index.md
index ba250af2720f..72c41123f1a2 100644
--- a/docs/src/pages/guides/guide-riot/index.md
+++ b/docs/src/pages/guides/guide-riot/index.md
@@ -88,7 +88,7 @@ Now create a `../src/index.stories.js` file, and write your first story like thi
 import { tag, mount } from '@storybook/riot';
 import SimpleTestRaw from './SimpleTest.txt'; //can be loaded as string if you prefer
 import './AnotherTest.tag';
-//if you need to import .tag files as text, just use the raw-loader instead of the riot-tag-loader
+//if you need to import .tag files as text, use the raw-loader instead of the riot-tag-loader
 
 export default { title: 'My Component' };
   
diff --git a/docs/src/pages/guides/guide-svelte/index.md b/docs/src/pages/guides/guide-svelte/index.md
index 0082133d9f65..6d19073af4b0 100644
--- a/docs/src/pages/guides/guide-svelte/index.md
+++ b/docs/src/pages/guides/guide-svelte/index.md
@@ -89,7 +89,7 @@ export const withEmoji = () => ({
 Svelte storybooks don't support using templates in a story yet. 
 Instead, you can create a `.svelte` file to compose components together, or to access all normal Svelte functionality, like slots.
 
-So you can create a story "view" file, essentially just a .svelte file to load your components into to test.
+So you can create a story "view" file, which is essentially a .svelte file to load your components into to test.
 
 ```html
 <!-- MyButtonView  -->
diff --git a/docs/src/pages/testing/automated-visual-testing/index.md b/docs/src/pages/testing/automated-visual-testing/index.md
index 92a4e2ca4e0c..2e537a41b3cf 100644
--- a/docs/src/pages/testing/automated-visual-testing/index.md
+++ b/docs/src/pages/testing/automated-visual-testing/index.md
@@ -20,7 +20,7 @@ For example, changes in [anti-aliasing](https://en.wikipedia.org/wiki/Spatial_an
 ![Menu before and after differences](../static/image-diff-1.png)
 ![Close-up of menu before and after differences](../static/image-diff-2.png)
 
-Even though we didn't change any CSS and the menus appear visually the same to our eyes, if we just compare their pixels 1:1 we find that lots of it has changed! This can happen between browser versions, underlying hardware changes on your cloud platform, and more.
+Even though we didn't change any CSS and the menus appear visually the same to our eyes, if we compare their pixels 1:1 we find that lots of it has changed! This can happen between browser versions, underlying hardware changes on your cloud platform, and more.
 
 Similar situations happen all the time, such as how images, drop shadows, etc are rendered.
 
diff --git a/examples-native/crna-kitchen-sink/App.js b/examples-native/crna-kitchen-sink/App.js
index cf409b5aa655..51a052035833 100644
--- a/examples-native/crna-kitchen-sink/App.js
+++ b/examples-native/crna-kitchen-sink/App.js
@@ -4,7 +4,7 @@ export { StorybookUIRoot as default };
 
 // NOTE: The code below is what CRNA generates out of the box. We currently
 // have no clever way of replacing this with Storybook's UI (Vanilla RN does!)
-// so for now we just replace the code outright. Keeping this here for clarity.
+// so for now we replace the code outright. Keeping this here for clarity.
 //
 // import React from 'react';
 // import { StyleSheet, Text, View } from 'react-native';
diff --git a/examples/dev-kits/config.js b/examples/dev-kits/config.js
index 507b2b6ae9b9..51d216a42df9 100644
--- a/examples/dev-kits/config.js
+++ b/examples/dev-kits/config.js
@@ -1,6 +1,6 @@
 import { configure } from '@storybook/react';
 
-// The simplest version of examples would just export this function for users to use
+// The simplest version of examples would export this function for users to use
 function importAll(context) {
   context.keys().forEach(filename => context(filename));
 }
diff --git a/lib/api/src/store.ts b/lib/api/src/store.ts
index e77a4891a867..5d4428bce183 100644
--- a/lib/api/src/store.ts
+++ b/lib/api/src/store.ts
@@ -91,7 +91,7 @@ export default class Store {
     // What did the patch actually return
     let delta: Patch = {};
     if (typeof inputPatch === 'function') {
-      // Pass the same function, but just set delta on the way
+      // Pass the same function, but set delta on the way
       patch = (state: State) => {
         const getDelta = inputPatch as InputFnPatch;
         delta = getDelta(state);
diff --git a/lib/cli/README.md b/lib/cli/README.md
index 4f5c83d1c6af..c556bcc81fe1 100644
--- a/lib/cli/README.md
+++ b/lib/cli/README.md
@@ -4,7 +4,7 @@ Storybook CLI (_Command Line Interface_) is the easiest way to add [Storybook](h
 
 ![Screenshot](docs/getstorybook.png)
 
-Just go to your project and run:
+Go to your project and run:
 
 ```sh
 cd my-app
diff --git a/lib/cli/test/fixtures/ember-cli/README.md b/lib/cli/test/fixtures/ember-cli/README.md
index ad3c1ebbdb74..608bce41c28c 100644
--- a/lib/cli/test/fixtures/ember-cli/README.md
+++ b/lib/cli/test/fixtures/ember-cli/README.md
@@ -1,7 +1,7 @@
 # ember-fixture
 
 This README outlines the details of collaborating on this Ember application.
-A short introduction of this app could easily go here.
+A short introduction of this app could go here.
 
 ## Prerequisites
 
diff --git a/lib/cli/test/fixtures/react_scripts/README.md b/lib/cli/test/fixtures/react_scripts/README.md
index f7d4c2fc41fc..53be922fcbf4 100644
--- a/lib/cli/test/fixtures/react_scripts/README.md
+++ b/lib/cli/test/fixtures/react_scripts/README.md
@@ -369,7 +369,7 @@ Alternatively you may use `yarn`:
 yarn add react-router
 ```
 
-This works for any library, not just `react-router`.
+This works for any library, not only `react-router`.
 
 ## Importing a Component
 
@@ -1203,7 +1203,7 @@ Jest will look for test files with any of the following popular naming conventio
 
 The `.test.js` / `.spec.js` files (or the `__tests__` folders) can be located at any depth under the `src` top level folder.
 
-We recommend to put the test files (or `__tests__` folders) next to the code they are testing so that relative imports appear shorter. For example, if `App.test.js` and `App.js` are in the same folder, the test just needs to `import App from './App'` instead of a long relative path. Colocation also helps find tests more quickly in larger projects.
+We recommend to put the test files (or `__tests__` folders) next to the code they are testing so that relative imports appear shorter. For example, if `App.test.js` and `App.js` are in the same folder, the test needs to `import App from './App'` instead of a long relative path. Colocation also helps find tests more quickly in larger projects.
 
 ### Command Line Interface
 
@@ -1347,7 +1347,7 @@ and then use them in your tests like you normally do.
 
 > Note: this feature is available with `react-scripts@0.4.0` and higher.
 
-If your app uses a browser API that you need to mock in your tests or if you just need a global setup before running your tests, add a `src/setupTests.js` to your project. It will be automatically executed before running your tests.
+If your app uses a browser API that you need to mock in your tests or if you need a global setup before running your tests, add a `src/setupTests.js` to your project. It will be automatically executed before running your tests.
 
 For example:
 
@@ -1495,7 +1495,7 @@ For an example, a simple button component could have following states:
 
 Usually, it’s hard to see these states without running a sample app or some examples.
 
-Create React App doesn’t include any tools for this by default, but you can easily add [Storybook for React](https://storybook.js.org) ([source](https://github.com/storybookjs/storybook)) or [React Styleguidist](https://react-styleguidist.js.org/) ([source](https://github.com/styleguidist/react-styleguidist)) to your project. **These are third-party tools that let you develop components and see all their states in isolation from your app**.
+Create React App doesn’t include any tools for this by default, but you can add [Storybook for React](https://storybook.js.org) ([source](https://github.com/storybookjs/storybook)) or [React Styleguidist](https://react-styleguidist.js.org/) ([source](https://github.com/styleguidist/react-styleguidist)) to your project. **These are third-party tools that let you develop components and see all their states in isolation from your app**.
 
 ![Storybook for React Demo](http://i.imgur.com/7CIAWpB.gif)
 
@@ -1637,7 +1637,7 @@ it may take up to 24 hours for the cache to be invalidated.
     this messages is currently left as an exercise to the developer, but as a
     starting point, you can make use of the logic included in [`src/registerServiceWorker.js`](src/registerServiceWorker.js), which
     demonstrates which service worker lifecycle events to listen for to detect each
-    scenario, and which as a default, just logs appropriate messages to the
+    scenario, and which as a default, logs appropriate messages to the
     JavaScript console.
 
 7.  By default, the generated service worker file will not intercept or cache any
@@ -1828,7 +1828,7 @@ Then run the `firebase init` command from your project’s root. You need to cho
 
     First, let's associate this project directory with a Firebase project.
     You can create multiple project aliases by running firebase use --add,
-    but for now we'll just set up a default project.
+    but for now we'll set up a default project.
 
     ? What Firebase project do you want to associate as default? Example app (example-app-fd690)
 
diff --git a/lib/cli/test/fixtures/update_package_organisations/README.md b/lib/cli/test/fixtures/update_package_organisations/README.md
index 2da029bd501c..ddaf37cd5e60 100644
--- a/lib/cli/test/fixtures/update_package_organisations/README.md
+++ b/lib/cli/test/fixtures/update_package_organisations/README.md
@@ -849,7 +849,7 @@ Since Create React App doesn’t support server rendering, you might be wonderin
     <meta property="og:description" content="__OG_DESCRIPTION__">
 ```
 
-Then, on the server, regardless of the backend you use, you can read `index.html` into memory and replace `__OG_TITLE__`, `__OG_DESCRIPTION__`, and any other placeholders with values depending on the current URL. Just make sure to sanitize and escape the interpolated values so that they are safe to embed into HTML!
+Then, on the server, regardless of the backend you use, you can read `index.html` into memory and replace `__OG_TITLE__`, `__OG_DESCRIPTION__`, and any other placeholders with values depending on the current URL. Make sure to sanitize and escape the interpolated values so that they are safe to embed into HTML!
 
 If you use a Node server, you can even share the route matching logic between the client and the server. However duplicating it also works fine in simple cases.
 
@@ -901,7 +901,7 @@ Jest will look for test files with any of the following popular naming conventio
 
 The `.test.js` / `.spec.js` files (or the `__tests__` folders) can be located at any depth under the `src` top level folder.
 
-We recommend to put the test files (or `__tests__` folders) next to the code they are testing so that relative imports appear shorter. For example, if `App.test.js` and `App.js` are in the same folder, the test just needs to `import App from './App'` instead of a long relative path. Colocation also helps find tests more quickly in larger projects.
+We recommend to put the test files (or `__tests__` folders) next to the code they are testing so that relative imports appear shorter. For example, if `App.test.js` and `App.js` are in the same folder, the test needs to `import App from './App'` instead of a long relative path. Colocation also helps find tests more quickly in larger projects.
 
 ### Command Line Interface
 
@@ -1167,7 +1167,7 @@ For an example, a simple button component could have following states:
 
 Usually, it’s hard to see these states without running a sample app or some examples.
 
-Create React App doesn’t include any tools for this by default, but you can easily add [React Storybook](https://github.com/kadirahq/react-storybook) to your project. **It is a third-party tool that lets you develop components and see all their states in isolation from your app**.
+Create React App doesn’t include any tools for this by default, but you can add [React Storybook](https://github.com/kadirahq/react-storybook) to your project. **It is a third-party tool that lets you develop components and see all their states in isolation from your app**.
 
 ![React Storybook Demo](http://i.imgur.com/7CIAWpB.gif)
 
@@ -1305,7 +1305,7 @@ Then run the `firebase init` command from your project’s root. You need to cho
 
     First, let's associate this project directory with a Firebase project.
     You can create multiple project aliases by running firebase use --add,
-    but for now we'll just set up a default project.
+    but for now we'll set up a default project.
 
     ? What Firebase project do you want to associate as default? Example app (example-app-fd690)
 
@@ -1511,7 +1511,7 @@ See this [blog post](https://medium.com/@omgwtfmarc/deploying-create-react-app-t
 
 ### Surge
 
-Install the Surge CLI if you haven’t already by running `npm install -g surge`. Run the `surge` command and log in you or create a new account. You just need to specify the _build_ folder and your custom domain, and you are done.
+Install the Surge CLI if you haven’t already by running `npm install -g surge`. Run the `surge` command and log in you or create a new account. You need to specify the _build_ folder and your custom domain, and you are done.
 
 ```sh
               email: email@domain.com
diff --git a/lib/client-api/src/story_store.ts b/lib/client-api/src/story_store.ts
index 82111d1591c6..a117ec9727b5 100644
--- a/lib/client-api/src/story_store.ts
+++ b/lib/client-api/src/story_store.ts
@@ -121,7 +121,7 @@ export default class StoryStore extends EventEmitter {
 
   extract(options?: StoryOptions) {
     const stories = Object.entries(this._data);
-    // determine if we should apply a sort to the stories or just use default import order
+    // determine if we should apply a sort to the stories or use default import order
     if (Object.values(this._data).length > 0) {
       const index = Object.keys(this._data).find(
         key =>
diff --git a/lib/codemod/src/transforms/update-addon-info.js b/lib/codemod/src/transforms/update-addon-info.js
index 60fda47e7b16..1417e7fe88a8 100644
--- a/lib/codemod/src/transforms/update-addon-info.js
+++ b/lib/codemod/src/transforms/update-addon-info.js
@@ -37,7 +37,7 @@ export default function transformer(file, api) {
   const getOptions = args => {
     if (args[3] === undefined) {
       if (args[2] === undefined) {
-        // when the optional description string is not supplied for addWithInfo, just use story name
+        // when the optional description string is not supplied for addWithInfo, use story name
         return [args[0]];
       }
       return [args[1]];