Ver código fonte

Docs: Minor corrections in Custom builds and Installing plugins. [skip ci]

Anna Tomanek 7 anos atrás
pai
commit
d64969b36f

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

@@ -46,7 +46,7 @@ git remote add upstream https://github.com/ckeditor/ckeditor5-build-classic.git
 <info-box hint>
 	If you do not want to fork the official build, you can just clone it. However, you will not be able to commit and push your customizations back to GitHub.
 
-	Alternatively, instead of creating a custom build you can {@link builds/guides/integration/advanced-setup#scenario-2-building-from-source integrate CKEditor 5 directly from source}. This option allows even greater flexibility and requires less overhead (you will not need to fork the official build). However, it requires that you fully control the `webpack.config.js` file (which is not that easy in some environments – e.g. in [`angular-cli`](https://cli.angular.io/) or [`create-react-app`](https://github.com/facebook/create-react-app)).
+	Alternatively, instead of creating a custom build you can {@link builds/guides/integration/advanced-setup#scenario-2-building-from-source integrate CKEditor 5 directly from source}. This option allows for even more flexibility and requires less overhead (you will not need to fork the official build). However, it requires that you fully control the `webpack.config.js` file (which is not that easy in some environments &mdash; for example in [`angular-cli`](https://cli.angular.io/) or [`create-react-app`](https://github.com/facebook/create-react-app)).
 </info-box>
 
 <info-box warning>
@@ -58,7 +58,7 @@ git remote add upstream https://github.com/ckeditor/ckeditor5-build-classic.git
 Every build contains the following files:
 
 * `build/ckeditor.js` &ndash; The ready-to-use editor bundle, containing the editor and all plugins.
-* `src/ckeditor.js` &ndash; The source entry point of the build. Based on it the `build/ckeditor.js` file is created by [webpack](https://webpack.js.org). It defines the editor creator, a list of plugins and the default config of a build.
+* `src/ckeditor.js` &ndash; The source entry point of the build. Based on it the `build/ckeditor.js` file is created by [webpack](https://webpack.js.org). It defines the editor creator, the list of plugins and the default configuration of a build.
 * `webpack-config.js` &ndash; webpack configuration used to build the editor.
 
 ## Customizing a build
@@ -95,7 +95,7 @@ This will install the package and add it to `package.json`. You can also edit `p
 
 If you added or removed dependencies, you will also need to modify the `src/ckeditor.js` file.
 
-Every plugin that you want to include in the bundle should be included at this stage. You can also change the editor creator and specify the default editor configuration. For instance, your webpack entry file (`src/ckeditor.js`) may look like this:
+Every plugin that you want to include in the bundle should be added at this stage. You can also change the editor creator and specify the default editor configuration. For instance, your webpack entry file (`src/ckeditor.js`) may look like this:
 
 ```js
 'use strict';

+ 6 - 6
docs/builds/guides/integration/installing-plugins.md

@@ -29,7 +29,7 @@ Adding plugins to existing builds is done through their customization. Editor bu
 3. Add it to the build configuration.
 4. Bundle the build.
 
-```
+```bash
 git clone -b stable https://github.com/ckeditor/ckeditor5-build-classic.git
 cd ckeditor5-build-classic
 npm install
@@ -37,7 +37,7 @@ npm install
 
 Now, install the plugin package:
 
-```
+```bash
 npm install --save-dev @ckeditor/ckeditor5-alignment
 ```
 
@@ -122,7 +122,7 @@ ClassicEditor.defaultConfig = {
 
 Finally, bundle the build:
 
-```
+```bash
 npm run build
 ```
 
@@ -142,7 +142,7 @@ If you {@link framework/guides/quick-start build the editor from source}, then t
 
 For example, if you wish to install the text alignment feature:
 
-```
+```bash
 npm install --save-dev @ckeditor/ckeditor5-alignment
 ```
 
@@ -200,7 +200,7 @@ ClassicEditor
 	} );
 ```
 
-All this works because a typical `src/ckeditor.js` module that you can find in every editor build repository (see e.g. [`@ckeditor/ckeditor5-build-classic`](https://github.com/ckeditor/ckeditor5-build-classic/blob/stable/src/ckeditor.js)) looks like this:
+All this works because a typical `src/ckeditor.js` module that you can find in every editor build repository (see for example [`@ckeditor/ckeditor5-build-classic`](https://github.com/ckeditor/ckeditor5-build-classic/blob/stable/src/ckeditor.js)) looks like this:
 
 ```js
 import ClassicEditorBase from '@ckeditor/ckeditor5-editor-classic/src/classiceditor';
@@ -236,7 +236,7 @@ ClassicEditor.defaultConfig = {
 };
 ```
 
-This code imports the source of the classic editor and extends it with a static `builtinPlugins` and `defaultConfig` properties in which it defines a set of plugins and configuration to be used by this editor class.
+This code imports the source of the classic editor and extends it with a static `builtinPlugins` and `defaultConfig` properties where it defines a set of plugins and configuration to be used by this editor class.
 
 In this approach, all editor instances created by using this editor build will by default load all these built-in plugins and configuration.