Преглед изворни кода

Docs: Fixed some links found by improved link validation.

Piotrek Koszuliński пре 8 година
родитељ
комит
a58228aa25

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

@@ -396,7 +396,7 @@ Note: The number of options was reduced on purpose. We understood that configuri
 </tr>
 <tr>
 <td><a href="/ckeditor4/docs/#!/api/CKEDITOR.config-cfg-on">on</a></td>
-<td><p>Using configuration file/setting to define event listeners was a bad practice so the support for it has been dropped.</p><p>When creating an editor, a <code>Promise</code> is returned. Use <code>then/catch</code> to define a callback when editor is initialised or fails to start. The promise returns the created editor instance, e.g. {@link module:editor-classic/classiceditor~ClassicEditor <code>ClassicEditor</code>}, you can listen to various {@link module:editor-classic/classiceditor~ClassicEditor#Events events} there.</p><p>Note: the editor instance is not the only object on which events are fired. You can also listen to e.g. {@link module:engine/model/document~Document#Events <code>Document</code> events}.</p></td>
+<td><p>Using configuration file/setting to define event listeners was a bad practice so the support for it has been dropped.</p><p>When creating an editor, a <code>Promise</code> is returned. Use <code>then/catch()</code> to define a callback when the editor is initialized or fails to start. The promise returns the created editor instance, e.g. {@link module:editor-classic/classiceditor~ClassicEditor <code>ClassicEditor</code>}, on which you can listen to its events.</p><p>Note: the editor instance is not the only object on which events are fired. You can also listen to e.g. {@link module:engine/model/document~Document `Document`} events.</p></td>
 </tr>
 <tr>
 <td><a href="/ckeditor4/docs/#!/api/CKEDITOR.config-cfg-pasteFilter">pasteFilter</a></td>

+ 3 - 3
docs/framework/guides/architecture/core-editor-architecture.md

@@ -15,7 +15,7 @@ The {@link module:core/editor/editor~Editor} class represents the base of the ed
 * {@link module:core/editor/editor~Editor#plugins} and {@link module:core/editor/editor~Editor#commands} &ndash; The collection of loaded plugins and commands.
 * {@link module:core/editor/editor~Editor#model} &ndash; The entry point to editor's abstract data model.
 * {@link module:core/editor/editor~Editor#data} &ndash; The data controller. It controls how data is retrieved from the document and set inside it.
-* {@link module:core/editor/editor~Editor#editing} &ndash; The editing controller. It controls {@link module:engine/controller/editingcontroller~EditingController#document document} rendering, including selection handling.
+* {@link module:core/editor/editor~Editor#editing} &ndash; The editing controller. It controls {@link module:engine/model/model~Model#document document} rendering, including selection handling.
 * {@link module:core/editor/editor~Editor#keystrokes} &ndash; The keystroke handler. It allows to bind keystrokes to actions.
 
 Besides that, the editor exposes a few of methods:
@@ -109,9 +109,9 @@ refresh() {
 }
 ```
 
-This method is automatically called (by the command itself) when {@link module:engine/model/document~Document#event:changesDone any changes are applied to the model}. This means that the command automatically refreshes its own state when anything changes in the editor.
+This method is automatically called (by the command itself) when {@link module:engine/model/document~Document#event:change any changes are applied to the model}. This means that the command automatically refreshes its own state when anything changes in the editor.
 
-The important thing about commands is that every change in their state as well as calling the `execute()` method fires an event (e.g. {@link module:core/command~Command#event:change:{attribute} `change:value`} or {@link module:core/command~Command#event:execute `execute`}).
+The important thing about commands is that every change in their state as well as calling the `execute()` method fires an event (e.g. {@link module:core/command~Command#event-change:{property} `change:value`} or {@link module:core/command~Command#event:execute `execute`}).
 
 These events make it possible to control the command from the outside. For instance, if you want to disable specific commands when some condition is true (for example, according to your application's logic, they should be temporarily disabled) and there is no other, cleaner way to do that, you can block the command manually: