Parcourir la source

Merge branch 'master' into t/450

Piotrek Koszuliński il y a 8 ans
Parent
commit
5788c14274

+ 15 - 15
docs/builds/guides/integration/basic-api.md

@@ -9,21 +9,21 @@ order: 20
 
 ## Creators
 
-Each CKEditor 5 build provides a class that handles the creation of editor instances inside a page. For this reason they’re called “creators”. Every creator comes with a static `create()` method.
+Each CKEditor 5 build provides a class that handles the creation of editor instances inside a page. For this reason they are called "creators". Every creator comes with a static `create()` method.
 
 The following are creator class names for each build:
 
-* Classic Editor: {@link module:editor-classic/classiceditor~ClassicEditor}
-* Inline Editor: {@link module:editor-inline/inlineeditor~InlineEditor}
-* Medium-like Editor: {@link module:editor-medium-like/mediumlikeeditor~MediumLikeEditor}
+* Classic Editor – {@link module:editor-classic/classiceditor~ClassicEditor}
+* Inline Editor – {@link module:editor-inline/inlineeditor~InlineEditor}
+* Medium-like Editor – {@link module:editor-medium-like/mediumlikeeditor~MediumLikeEditor}
 
-Most of the examples in the documentation use the `ClassicEditor` class, but things should work in similar way with other creator classes.
+Most of the examples in the documentation use the `ClassicEditor` class, but things should work in a similar way with other creator classes.
 
 Because builds are distributed as [UMD modules](https://github.com/umdjs/umd), these classes can be retrieved:
 
-* by [CommonJS](http://wiki.commonjs.org/wiki/CommonJS) compatible loader (e.g. [Webpack](https://webpack.js.org) or [Browserify](http://browserify.org/)),
+* by a [CommonJS](http://wiki.commonjs.org/wiki/CommonJS)-compatible loader (e.g. [Webpack](https://webpack.js.org) or [Browserify](http://browserify.org/)),
 * by [RequireJS](http://requirejs.org/) (or any other AMD library),
-* from the global namespace if none of the above loaders is not available.
+* from the global namespace if none of the above loaders is available.
 
 For example:
 
@@ -41,13 +41,13 @@ require( '/(ckeditor path)/build/ckeditor.js', ClassicEditor => {
 ClassicEditor.create; // [Function]
 ```
 
-Having the above in mind, depending on which build you’re using, creating an editor in the page is a breeze:
+Depending on which build you are using, creating an editor in the page is then a breeze:
 
-In the HTML:
+In the HTML code:
 
 ```html
 <textarea id="text-editor">
-	&lt;p&gt;Here goes the initial contents of the editor.&lt;/p&gt;
+	&lt;p&gt;Here goes the initial content of the editor.&lt;/p&gt;
 </textarea>
 ```
 
@@ -63,21 +63,21 @@ ClassicEditor.create( document.querySelector( '#text-editor' ) )
 	} );
 ```
 
-In the above case, the `<textarea>` element is hidden and replaced with an editor. The `<textarea>` data is used to initialize the editor contents. A `<div>` element could have been used in the same fashion.
+In the above case, the `<textarea>` element is hidden and replaced with an editor. The `<textarea>` data is used to initialize the editor content. A `<div>` element can be used in the same fashion.
 
 <side-box info>
 	Every creator may accept different parameters and handle initialization differently. For instance, the classic editor will replace a given element with an editor, while the inline editor will use the given element to initialize the editor on it. See each editor's documentation to learn the details.
 
-	The interface of the editor class isn't enforced either. Since different implementations of editors may vary heavily in terms of functionality, the editor class implementers have full freedom regarding the API. Therefore, the examples in this guide may not work with some editor classes.
+	The interface of the editor class is not enforced either. Since different implementations of editors may vary heavily in terms of functionality, the editor class implementers have full freedom regarding the API. Therefore, the examples in this guide may not work with some editor classes.
 </side-box>
 
 ## Interacting with the editor
 
-Once the editor is created, it is possible to interact with it through its API. The `editor` variable, from the above examples, should enable that.
+Once the editor is created, it is possible to interact with it through its API. The `editor` variable from the examples above should enable that.
 
 ### Setting the editor data
 
-To replace the editor contents with new data, just use the `setData` method:
+To replace the editor content with new data, just use the `setData` method:
 
 ```js
 editor.setData( '<p>Some text.</p>' );
@@ -85,7 +85,7 @@ editor.setData( '<p>Some text.</p>' );
 
 ### Getting the editor data
 
-If the editor contents need to be retrieved for any reason, like for the scope of sending it to the server through an Ajax call, simply use the `getData` method:
+If the editor content needs to be retrieved for any reason, like for sending it to the server through an Ajax call, simply use the `getData` method:
 
 ```js
 const data = editor.getData();

+ 8 - 8
docs/builds/guides/integration/configuration.md

@@ -1,7 +1,7 @@
 ---
 # Scope:
 # * Introduction on how to set configurations.
-# * Introduction on the top/must-know configurations.
+# * Introduction to the top and must-know configurations.
 # * Point where to find the list of configuration options.
 
 title: Configuration
@@ -9,7 +9,7 @@ category: builds-integration
 order: 30
 ---
 
-When creating an editor in your page, it is possible to setup configurations that changes many of its aspects. For example:
+When creating an editor in your page, it is possible to set up configurations that change many of its aspects. For example:
 
 ```js
 ClassicEditor
@@ -22,11 +22,11 @@ ClassicEditor
 	} );
 ```
 
-As you can see, configurations are set by a simple JavaScript object passed to the editor creator class. It works in the same fashion when the create method is used instead.
+As you can see, configurations are set by a simple JavaScript object passed to the editor creator class. It works in the same way when the `create()` method is used instead.
 
 ## Enabling features
 
-Builds come with all features included in the distribution package enabled by default. Theyre defined as plugins for CKEditor.
+Builds come with all features included in the distribution package enabled by default. They are defined as plugins for CKEditor.
 
 In some cases, you may need to have different editor setups in your application, all based on the same build. For that purpose, you need to control the plugins available in an editor at runtime. The following are a few examples:
 
@@ -53,7 +53,7 @@ ClassicEditor
 ```
 
 <side-box tip>
-	If a build contains too many or too few features, the best approach is creating a custom build instead of simply using configurations.
+	If a build contains too many or too few features, the best approach is to create a custom build instead of simply using configurations.
 </side-box>
 
 ### List of plugins
@@ -66,9 +66,9 @@ ClassicEditor.build.plugins.map( plugin => plugin.pluginName );
 
 ## Toolbar setup
 
-On builds that contain toolbars, an optimal default configuration is defined for it. You may need a different toolbar arrangement though and this can be achieved through configuration.
+In builds that contain toolbars an optimal default configuration is defined for it. You may need a different toolbar arrangement, though, and this can be achieved through configuration.
 
-Each creator may have a different toolbar configuration scheme, so it is recommended to check the creator API documentation. In any case, the following example may give you a general idea of it:
+Each creator may have a different toolbar configuration scheme, so it is recommended to check the creator API documentation. In any case, the following example may give you a general idea:
 
 ```js
 ClassicEditor
@@ -81,7 +81,7 @@ ClassicEditor
 ```
 
 <side-box tip>
-	The above is a strict UI related configuration. Removing a toolbar item don’t remove the feature from the editor internals. If you goal with the toolbar configuration is removing features, the right solution is removing their relative plugins. Check [Enabling features](#Enabling-features) above for more information.
+	The above is a strict UI-related configuration. Removing a toolbar item does not remove the feature from the editor internals. If your goal with the toolbar configuration is to remove features, the right solution is to remove their relative plugins. Check [Enabling features](#Enabling-features) above for more information.
 </side-box>
 
 <!-- TODO Add section about other configuration options. -->

+ 12 - 12
docs/builds/guides/integration/installation.md

@@ -9,25 +9,25 @@ order: 10
 
 ## Download options
 
-The goal of installing any of the CKEditor 5 builds is enabling you to using its API when integrating it inside your application. For that purpose, several options are available:
+The goal of installing any of the CKEditor 5 builds is to enable you to use its API when integrating it inside your application. For that purpose, several options are available:
 
 * [Zip download](#Zip-download)
 * [CDN](#CDN)
 * [npm](#npm)
 
-Each of the builds have independent release packages. Before starting, you must define which one you’re interested on. Check the Overview page for the list of available builds.
+Each of the builds has independent release packages. Before starting, you must define which one you are interested in. Check the {@link TODO Overview} page for the list of available builds.
 
 ### Zip download
 
-Go to http://ckeditor.com/ckeditor5-builds/download and download the build your prefered build. For example, you may download the `ckeditor5-build.classic-1.0.0.zip` file for the Classic Editor build.
+Go to http://ckeditor.com/ckeditor5-builds/download and download your preferred build. For example, you may download the `ckeditor5-build.classic-1.0.0.zip` file for the Classic Editor build.
 
-Extract the above zip file into a dedicated directory inside your website/application.
+Extract the above `.zip` file into a dedicated directory inside your website or application.
 
-The main entry point script will be then available are `<your-path>/ckeditor/build/ckeditor.js`.
+The main entry point script will then be available at `<your-path>/ckeditor/build/ckeditor.js`.
 
 ### CDN
 
-Builds can be loaded inside pages directly from our CDN, which is optimized for worldwide super-fast speed download.
+Builds can be loaded inside pages directly from our CDN, which is optimized for worldwide super fast download.
 
 Check out the {@link TODO CKEditor 5 Builds CDN website} for a list of URL entry points for the builds API.
 
@@ -35,21 +35,21 @@ Check out the {@link TODO CKEditor 5 Builds CDN website} for a list of URL entry
 
 All builds are released on npm. The following search shows all build packages available there: https://www.npmjs.com/search?q=%40ckeditor%2Fckeditor5-build
 
-Installing a build with npm is as simple as calling the following inside your website/application:
+Installing a build with npm is as simple as calling the following inside your website or application:
 
 ```
 npm install --save @ckeditor/ckeditor5-build-classic
 ```
 
-The script entry point for the build class will be found then at `node_modules/ckeditor5-build-classic/build/ckeditor.js`.
+The script entry point for the build class will then be found at `node_modules/ckeditor5-build-classic/build/ckeditor.js`.
 
-## Included Files
+## Included files
 
 The following are the main files available in all build distributions:
 
-* `build/ckeditor.js`: the main UMD distribution script, containing the editor core and all plugins. Compatible with ECMAScript 6 enabled browsers. A smaller download.
-* `build/ckeditor.compat.js`: the same as the above, for browsers not compatible with ES6.
-* `ckeditor.js`: the source entry point of the build. Can be used for complex bundling and development.
+* `build/ckeditor.js` &ndash; The main UMD distribution script, containing the editor core and all plugins. Compatible with ECMAScript 6 enabled browsers. A smaller download.
+* `build/ckeditor.compat.js` &ndash; The same as the above, for browsers not compatible with ES6.
+* `ckeditor.js`: &ndash; The source entry point of the build. It can be used for complex bundling and development.
 
 ## Loading the API
 

+ 15 - 15
docs/builds/guides/integration/plugins.md

@@ -1,6 +1,6 @@
 ---
 # Scope:
-# * Introduction on plugins.
+# * Introduction to plugins.
 # * Exemplify use cases.
 # * Point to resources to learn plugins development.
 
@@ -9,35 +9,35 @@ category: builds-integration
 order: 40
 ---
 
-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 a predefined collection of plugins, put together to satisfy specific needs.
+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 several grannular 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) packages contains several granular plugins).
 
 ## Common use cases
 
-Plugins can be pretty much anything. They’re simply code, initialized by the editor if they’re configured to be loaded. They can use the richness of the 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 code, initialized by the editor if they are configured to be loaded. They can use the richness of the {@link TODO CKEditor 5 Framework API} to enhance the editor or to better integrate it with your application.
 
 Common use cases for plugins are:
 
-* **Editing features**, like bold, heading, linking or whichever feature that interacts with the user on the manipulation of the contents.
-* **Adding semantic value** to the contents, like annotations or accessibility features.
-* **Third party services integration**, for injecting external resources inside the contents, like videos or social network posts.
+* **Editing features**, like bold, heading, linking or whichever feature that the user can use to manipulate the content.
+* **Adding semantic value** to the content, like annotations or accessibility features.
+* **Third-party services integration**, for injecting external resources inside 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 contents.
-* And other infinite possibilities
+* **Injecting analysis tools** that help enhancing the quality of the content.
+* And other infinite possibilities...
 
 ## Creating plugins
 
 Creating your own plugins is a straightforward task but it requires good knowledge about a few aspects of the CKEditor 5 development environment. The following resources are recommended as a starting point:
 
-* {@link TODO Plugin development guide}, in the CKEditor 5 Framework documentation.
-* {@link TODO Creating custom builds}, which is necessary to have your plugin included inside a CKEditor 5 build.
+* {@link TODO Plugin development guide} in the CKEditor 5 Framework documentation.
+* {@link TODO Creating custom builds} which is necessary to have your plugin included inside a CKEditor 5 build.
 
-A good understanding about the {@link TODO CKEditor 5 Framework} is also very welcome when it comes to creating plugins.
+A good understanding of the {@link TODO CKEditor 5 Framework} is also very welcome when it comes to creating plugins.
 
-## Using 3rd party plugins
+## Using third-party plugins
 
-A great way to enhance your builds with additional features is by using plugins created by the community. Such plugins are generally available as npm packages, so a quick [search on the “ckeditor5” keyword in npm](https://www.npmjs.com/search?q=ckeditor5) should work as a starting point.
+A great way to enhance your builds with additional features is by using plugins created by the community. Such plugins are generally available as npm packages, so a quick [search on the "ckeditor5" keyword in npm](https://www.npmjs.com/search?q=ckeditor5) should work as a starting point.
 
-Once you have plugins to be included, just {@link TODO create a custom build}, configured to include them.
+Once you have plugins to be included, just {@link TODO create a custom build} configured to include them.

+ 11 - 11
docs/builds/guides/migrate.md

@@ -9,47 +9,47 @@ category: builds-guides
 order: 30
 ---
 
-When compared to its previous versions, CKEditor 5 can be considered a totally new editor. Every single aspect of it has been redesigned, from installation, to integration, to features, to its data model, to its API. Therefore, moving applications using previous version to version 5 cannot be called simply “upgrade”. It is something bigger, so the “migration” term fits better.
+When compared to its previous versions, CKEditor 5 should be considered a totally new editor. Every single aspect of it was redesigned, from installation, to integration, to features, to its data model, and finally to its API. Therefore, moving applications using a previous version to version 5 cannot be simply called an "upgrade". It is something bigger, so the "migration" term fits better.
 
-There is no “drop in” solution for migrating. In this guide we hope to summarize the most important aspects to be taken in consideration.
+There is no "drop in" solution for migrating. In this guide we hope to summarize the most important aspects to be taken into consideration before you proceed with installing CKEditor 5.
 
 Before starting, be sure that migrating is your best choice. Check {@link TODO When NOT to use CKEditor 5 Builds}?
 
 ## Installation and integration
 
-The very first aspect that changed with CKEditor 5 is its installation procedure. It became much more modern, with introduction of modular patterns, UMD, npm, etc. Check {@link TODO Installation} for more details.
+The very first aspect that changed with CKEditor 5 is its installation procedure. It became much more modern with introduction of modular patterns, UMD, npm, etc. Check {@link TODO Installation} for more details.
 
-Once installed, the API for integrating CKEditor in your pages also changed. It's worth checking Basic API for an introduction.
+Once installed, the API for integrating CKEditor with your pages also changed. It is worth checking {@link TODO Basic API} for an introduction.
 
 ## Features
 
-When it comes to features, there are two aspects to be taken in consideration:
+When it comes to features, there are two aspects to be taken into consideration:
 
 * CKEditor 5 may still not have the same features available in CKEditor 4.
 * Existing features may behave differently.
 
-Therefore, it is worth spending good time analysing required features.
+Therefore, it is worth spending some time analyzing required features.
 
-CKEditor 5 has been designed with focus on creating quality content. Therefore, there are good reasons for it to not support some old features. You should take this chance to rethink features in your application, many times having to switch the approach towards a more modern reasoning.
+CKEditor 5 was designed with focus on creating quality content. There are thus good reasons for it to not support some old features. You should take this chance to rethink the features available in your application and in turn perhaps switch the approach towards a more modern reasoning.
 
 <!-- TODO 4 -->
 
 ## Plugins
 
-The trickiest migration challenge to be faced may be related to custom plugins you could have had developed for CKEditor 4. Although their concept may stay the same, their implementation is certainly different and will require rewriting them from scratch.
+The trickiest migration challenge to be faced may be related to custom plugins you could have developed for CKEditor 4. Although their concept may stay the same, their implementation is certainly different and will require rewriting them from scratch.
 
-The same may apply for third party plugins, which may not have been yet ported to CKEditor 5.
+The same may apply for third party plugins which may not have been ported to CKEditor 5 yet.
 
 Check the {@link TODO Plugins guide} for more information on the development of plugins.
 
 ## Themes (skins)
 
-In CKEditor 5, the previous concept of "skins” has been reviewed and is now called “themes”.
+In CKEditor 5, the previous concept of "skins" was reviewed and is now called "themes".
 
 If you have custom skins for CKEditor 4, these skins need to be recreated for CKEditor 5. Fortunately custom theming in CKEditor 5 is much more powerful and simpler than before. For more information, check how to {@link TODO create new themes in the CKEditor 5 Framework documentation}.
 
 ## Existing data
 
-An extremely important aspect to be remembered is that, because of the difference on features, data produced with CKEditor 4 may not be compatible with CKEditor 5.
+An extremely important aspect to be remembered is that &mdash; because of the difference in features &mdash; the data produced with CKEditor 4 may not be compatible with CKEditor 5.
 
 Extensive analysis, data verification and tests should be performed on existing data. If necessary, conversion procedures should be developed to avoid data loss.

+ 18 - 18
docs/builds/guides/overview.md

@@ -10,35 +10,35 @@ category: builds-guides
 order: 10
 ---
 
-CKEditor 5 Builds are comprised by a set of ready to use rich-text editors, so called "builds", in different configurations. Our goal is providing easy to use solutions that can satisfy good part of the editing use cases out there.
+CKEditor 5 Builds are comprised of a set of ready to use rich-text editors, so called "builds", with different configurations. Our goal is to provide easy to use solutions that can satisfy a good part of the editing use cases out there.
 
 ## Builds
 
 ### Classic editor
 
-The classic "boxed" editing interface, with toolbar at the top:
+The classic "boxed" editing interface, with a toolbar at the top:
 
-[ TODO: Classic Editor screenshot or sample ]
+[ TODO: Classic editor screenshot or sample ]
 
-### Inline Editor
+### Inline editor
 
-It leaves the contents as part of the page, attaching a floating toolbar to it:
+The edited content remains a part of the page, with a floating toolbar attached:
 
-[ TODO: Inline Editor screenshot ]
+[ TODO: Inline editor screenshot ]
 
 ## How builds are designed
 
-Each build has been designed to satisfy as many use cases as possible. They differ on their UI/UX and features, based on the following approach:
+Each build was designed to satisfy as many use cases as possible. They differ in their UI, UX and features, and are based on the following approach:
 
-* Include the set of features proposed by the Editor Recommendations project.
+* Include the set of features proposed by the {@link TODO Editor Recommendations} project.
 * Include features that contribute to creating quality content. In other words, features like fonts, colors and alignment are excluded.
 * Provide setups as generic as possible, based on research and community feedback.
 
-### Builds customization
+### Build customization
 
 Although the default builds try to fit many cases, they may still not be perfect in some integrations. They may have either too many or too few features. They may not have your preferred theme or UI implementation. Customization is required then.
 
-Check Customize and extend for in-depth details on how to change the default builds to match your needs and preferences.
+Check {@link TODO Custom builds} for details on how to change the default builds to match your preferences.
 
 ## Use cases
 
@@ -54,9 +54,9 @@ The following are **some** common use cases:
 	* Composing e-mail campaigns.
 	* Creating templates.
 * In forum applications:
-	* For the creation of topics and their replies.
-* In team collaboration application:
-	* For the creation of shared documents.
+	* Creation of topics and their replies.
+* In team collaboration applications:
+	* Creation of shared documents.
 * Other uses:
 	* User profile editing pages.
 	* Book writing applications.
@@ -67,13 +67,13 @@ The following are **some** common use cases:
 
 The {@link TODO CKEditor 5 Framework} should be used, instead of builds, in the following cases:
 
-* When you want to create your own text editor, having full control on every aspect of it, from UI to features.
-* When the solution proposed by the builds don't fit your specific use case.
+* When you want to create your own text editor and have full control over every aspect of it, from UI to features.
+* When the solution proposed by the builds does not fit your specific use case.
 
-{@link TODO CKEditor 4} should be used instead, in the following cases:
+In the following cases {@link TODO CKEditor 4} should be used instead:
 
-* When the compatibility with old browsers is a requirement.
+* When compatibility with old browsers is a requirement.
 * If CKEditor 4 contains features that are essential for you, which are not available in CKEditor 5 yet.
-* If CKEditor 4 is already in use in you application and you're still not ready to replace it with CKEditor 5.
+* If CKEditor 4 is already in use in you application and you are still not ready to replace it with CKEditor 5.
 
 <!-- TODO 1 -->

+ 24 - 17
docs/builds/guides/whats-new.md

@@ -1,7 +1,7 @@
 ---
 # Scope:
-# * Highlight new things, when compared to CKEditor 4.
-# * Emphasize cool new stuff were bringing, for those learning about CKEditor 5.
+# * Highlight new things when compared to CKEditor 4.
+# * Emphasize cool new stuff we are bringing, for those learning about CKEditor 5.
 
 title: What's new?
 category: builds-guides
@@ -10,33 +10,38 @@ order: 20
 
 ## Enhanced UX
 
+CKEditor 5 strives to provide a truly seamless, distraction-free editing experience to allow the users to focus on creating great content.
+
 ### Better images
 
-Inserting images inside the contents is now very intuitive, with all technical aspects (uploading, resizing) hidden from the user experience. No more complex dialogs.
+Inserting images into the content is now very intuitive, with all technical aspects (uploading, resizing) hidden from the user experience. No more complex dialogs.
 
-[ TODO Animated GIF of Pasting ]
+[ TODO Animated GIF of pasting ]
 
 [ TODO Animated GIF of DnD ]
 
-The outdated concept of image “alignment” has been dropped, introducing image “styles” instead:
+The outdated concept of image "alignment" was dropped in favor of image "styles":
 
-[ TODO Animated GIF on styles ]
+[ TODO Animated GIF of styles ]
 
 <!-- TODO 2 -->
 
 ### Simple linking
 
-No more complex dialogs for linking.
+No more complex dialogs for links.
 
 [ TODO Screenshot of a link with the edit balloon on it ]
 
 ### Auto formatting
 
-Start lists, headings and even bold text by typing.
+Start lists, headings and even bold text by typing, without the need to
+use toolbar buttons.
 
 [ TODO Animated GIF with auto formatting in action ]
 
-## Enhancement in the classic editor
+## Enhanced classic editor
+
+For CKEditor 5 we reinvented the concept of the "boxed" editor.
 
 ### New toolbar
 
@@ -44,23 +49,25 @@ The toolbar is now always visible when the user scrolls the page down.
 
 [ TODO Animated GIF with scrolling and toolbar ]
 
-### Inlined contents
+### Inlined content
 
-The contents of the editor are now placed inline in the page. It’s much easier to style them. Additionally, the editor grows with the contents (or not, it’s up to you!).
+The editor content is now placed inline in the page &mdash; it is now much easier to style it. Additionally, the editor grows with the content (or not, it is up to you!).
 
 [ TODO Animated GIF of the editor growing when typing ]
 
-## Less features == Better content
+## Less features == better content
 
 We focused on creating a tool for writing quality content. At the same time, we simplified the integration of the editor into your system.
 
-We had way too many features and configurations, which were confusing developers and at the same time negatively impacting on the end user experience. Misleading formatting tools have been removed, dialogs stripped out or simplified and well designed features that require no configuration.
+We feel that in previous editor versions we had way too many features and configurations. This was confusing developers and at the same time negatively impacting the end-user experience.
+
+In CKEditor 5 misleading formatting tools were removed, dialogs were stripped out or simplified in favor of well designed features that require no configuration.
 
 [ TODO Screenshot of the toolbar ]
 
 ## Lightweight
 
-The editor is much more lightweight and fast. It brings a great user experience on both desktop and mobile devices.
+The editor is much more lightweight and fast. It brings a fantastic user experience on both desktop and mobile devices.
 
 ## Highly customizable
 
@@ -68,14 +75,14 @@ CKEditor 5 Builds are based on the {@link TODO CKEditor 5 Framework}, which give
 
 ## Custom data model
 
-A much more efficient data model has been designed in CKEditor 5, making the development of features a much more creative experience and enhancing features like undo and redo.
+A much more efficient data model was designed for CKEditor 5. This makes the development of features a much more creative experience and improves features such as undo and redo.
 
 ## Collaborative editing
 
-Another important benefit of our custom data model is that it enables the possibility of real-time collaborative editing inside CKEditor, by introducing the concepts of “operations” and “operational transformations”. Read more about {@link TODO collaboration in the CKEditor 5 Framework documentation}.
+Another important benefit of the custom data model is that it enables the possibility of real-time collaborative editing inside CKEditor by introducing the concepts of "operations" and "operational transformations". Read more about {@link TODO collaboration in the CKEditor 5 Framework documentation}.
 
 <!-- TODO 3 -->
 
 ## Modern
 
-CKEditor 5 has been totally rewritten in ES6, using the power of modules. It provides all the necessary tools to easily integrate it with modern applications and technologies, like Angular, React, Node.js, npm, etc.
+CKEditor 5 has been totally rewritten in ES6, using the power of modules. It provides all the necessary tools to easily integrate it with modern applications and technologies like Angular, React, Node.js, npm, etc.