Docs: Fixed wrong EditorWithUI#element property docs formatting. [ski…

…p ci]

src/editor/editorwithui.jsdoc

@@ -28,22 +28,22 @@
  * @member {module:core/editor/editorui~EditorUI} #ui
  */
 
- /**
-  * The main (outermost) DOM element of the editor UI.
-  *
-  * For example, in {@link module:editor-classic/classiceditor~ClassicEditor} it is a `<div>` which
-  * wraps the editable element and the toolbar. In {@link module:editor-inline/inlineeditor~InlineEditor}
-  * it is the editable element itself (as there is no other wrapper). However, in
-  * {@link module:editor-decoupled/decouplededitor~DecoupledEditor} it is set to `null` because this editor does not
-  * come with a single "main" HTML element (its editable element and toolbar are separate).
-  *
-  * This property can be understood as a shorthand for retrieving the element that a specific editor integration
-  * considers to be its main DOM element. There are always other ways to access these elements, too
-  * (e.g. via {@link #ui `editor.ui`}).
-  *
-  * @readonly
-  * @member {HTMLElement|null} #element
-  */
+/**
+ * The main (outermost) DOM element of the editor UI.
+ *
+ * For example, in {@link module:editor-classic/classiceditor~ClassicEditor} it is a `<div>` which
+ * wraps the editable element and the toolbar. In {@link module:editor-inline/inlineeditor~InlineEditor}
+ * it is the editable element itself (as there is no other wrapper). However, in
+ * {@link module:editor-decoupled/decouplededitor~DecoupledEditor} it is set to `null` because this editor does not
+ * come with a single "main" HTML element (its editable element and toolbar are separate).
+ *
+ * This property can be understood as a shorthand for retrieving the element that a specific editor integration
+ * considers to be its main DOM element. There are always other ways to access these elements, too
+ * (e.g. via {@link #ui `editor.ui`}).
+ *
+ * @readonly
+ * @member {HTMLElement|null} #element
+ */
 
 /**
  * Fired when the editor UI is ready.