Browse Source

Docs: Corrections to Custom builds, Plugins, Installing plugins guides. [skip ci]

Anna Tomanek 7 years ago
parent
commit
114ea07749

+ 4 - 4
docs/builds/guides/development/custom-builds.md

@@ -50,7 +50,7 @@ git remote add upstream https://github.com/ckeditor/ckeditor5-build-classic.git
 </info-box>
 
 <info-box warning>
-	It is important that you use the `stable` branch of a build, not the `master` branch. The `master` branch might contain changes which are not yet compatible with the versions of CKEditor 5 source packages which were published on npm.
+	It is important that you use the `stable` branch of a build, not the `master` branch. The `master` branch might contain changes which are not yet compatible with the versions of CKEditor 5 source packages that were published on npm.
 </info-box>
 
 ## Build anatomy
@@ -72,13 +72,13 @@ In order to customize a build you need to:
 
 ### Installing dependencies
 
-First, you need to install dependencies which are already specified in build's `package.json`:
+First, you need to install dependencies which are already specified in the build's `package.json`:
 
 ```bash
 npm install
 ```
 
-Then, you can add missing depencies (i.e. packages you want to add to your build). The easiest way to do so is by typing:
+Then, you can add missing dependencies (i.e. packages you want to add to your build). The easiest way to do so is by typing:
 
 ```bash
 npm install --save-dev <package-name>
@@ -87,7 +87,7 @@ npm install --save-dev <package-name>
 This will install the package and add it to `package.json`. You can also edit `package.json` manually.
 
 <info-box hint>
-	Due to a non-deterministic way how npm installs packages, it is recommended to run `rm -rf node_modules && npm install` when in doubt. This will prevent some packages from getting installed more than once in `node_modules/` (which might lead to broken builds).
+	Due to the non-deterministic way how npm installs packages, it is recommended to run `rm -rf node_modules && npm install` when in doubt. This will prevent some packages from getting installed more than once in `node_modules/` (which might lead to broken builds).
 
 	You can also give [Yarn](https://yarnpkg.com/lang/en/) a try.
 </info-box>

+ 1 - 1
docs/builds/guides/development/installing-plugins.md

@@ -127,7 +127,7 @@ For example, if you wish to install the text aligment feature:
 npm install --save-dev @ckeditor/ckeditor5-alignment
 ```
 
-Edit the code which initializes the editor:
+Edit the code that initializes the editor:
 
 ```js
 import ClassicEditor from '@ckeditor/ckeditor5-editor-classic/src/classiceditor';

+ 3 - 3
docs/builds/guides/development/plugins.md

@@ -12,11 +12,11 @@ order: 20
 
 Features in CKEditor are introduced by plugins. In fact, without plugins CKEditor is an empty API with no use. The builds provided with CKEditor 5 are actually predefined collections of plugins, put together to satisfy specific needs.
 
-Plugins provided by the CKEditor core team are available in [npm](https://www.npmjs.com/search?q=ckeditor5) (and [GitHub](https://github.com/ckeditor?utf8=%E2%9C%93&q=ckeditor5&type=&language=), too) in form of npm packages. A package may contain one or more plugins (e.g. the [`@ckeditor/ckeditor5-image`](https://www.npmjs.com/package/@ckeditor/ckeditor5-image) packages contains {@link features/image several granular plugins}).
+Plugins provided by the CKEditor core team are available in [npm](https://www.npmjs.com/search?q=ckeditor5) (and [GitHub](https://github.com/ckeditor?utf8=%E2%9C%93&q=ckeditor5&type=&language=), too) in form of npm packages. A package may contain one or more plugins (e.g. the [`@ckeditor/ckeditor5-image`](https://www.npmjs.com/package/@ckeditor/ckeditor5-image) package contains {@link features/image several granular plugins}).
 
 ## Common use cases
 
-Plugins can be pretty much anything. They are simply pieces of code, initialized by the editor if they are configured to be loaded. They can use the richness of the {@link api/index CKEditor 5 Framework API} to enhance the editor or to better integrate it with your application.
+Plugins can be pretty much anything. They are simply pieces of code initialized by the editor if they are configured to be loaded. They can use the richness of the {@link api/index CKEditor 5 Framework API} to enhance the editor or to better integrate it with your application.
 
 Common use cases for plugins are:
 
@@ -25,7 +25,7 @@ Common use cases for plugins are:
 * **Third-party services integration**, for injecting external resources into the content, like videos or social network posts.
 * **Handling image upload** and image manipulation features.
 * **Providing widgets** for easy integration with application structured data.
-* **Injecting analysis tools** that help enhancing the quality of the content.
+* **Injecting analysis tools** that help enhance the quality of the content.
 * And other infinite possibilities...
 
 ## Creating plugins