Przeglądaj źródła

Docs: Minor corrections and improvements. [skip ci]

Piotrek Koszuliński 7 lat temu
rodzic
commit
8640ad2e31

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

@@ -59,7 +59,7 @@ For more information, check how to {@linkTODO create new themes in the CKEditor
 
 ## Existing data
 
-An extremely important aspect to be remembered is that — because of the difference in features — the **data produced with CKEditor 4 may not be compatible with CKEditor 5**.
+An extremely important aspect to be remembered is that — because of the difference in features — the **data produced with CKEditor 4 may not be compatible with CKEditor 5 (which may lead to data loss)**.
 
 Extensive analysis, data verification and tests should be performed on existing data. If necessary, you will need to develop conversion procedures to avoid data loss. A relatively simple yet efficient strategy of adopting CKEditor 5 into existing systems might be using CKEditor 5 for creating new content and the old editor for editing legacy content.
 

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

@@ -120,7 +120,7 @@ In the following cases [CKEditor 4](https://ckeditor.com/ckeditor-4/) should be
 
 * 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 are still not ready to replace it with CKEditor 5.
+* If CKEditor 4 is already in use in your application and you are still not ready to replace it with CKEditor 5.
 
 In the following cases [Letters](https://ckeditor.com/letters/) may be used instead:
 

+ 1 - 1
docs/builds/guides/support/browser-compatibility.md

@@ -37,7 +37,7 @@ Features known to not be fully supported yet:
 
 ## Mobile environment
 
-Although CKEditor 5 works in Safari for iOS and Chrome for Android, it has not been fully tested yet and there are known bugs and inconveniences. Full support for mobile browsers will be our goal after releasing 1.0.0.
+Although CKEditor 5 works in Safari for iOS and Chrome for Android, it has not been fully tested yet and there are known bugs and inconveniences. Full support for mobile browsers will be our goal after releasing v10.0.0.
 
 When working on mobile support we need to consider two complex aspects: