diff --git a/topics/products/phpstorm/php_open_api.md b/topics/products/phpstorm/php_open_api.md
index 4aa1f5e1b..b2f093372 100644
--- a/topics/products/phpstorm/php_open_api.md
+++ b/topics/products/phpstorm/php_open_api.md
@@ -22,7 +22,7 @@
 
 ### `PhpTypeProvider`
 
-Here is a code fragment that makes [PHPUnit field references in setUp support](https://youtrack.jetbrains.com/issue/WI-22143) work
+Here is a code fragment that makes [PHPUnit field references in setUp support](https://youtrack.jetbrains.com/issue/WI-22143) work.
 
 ```xml
 <php.typeProvider4
@@ -72,8 +72,8 @@ public interface PhpTypeProvider4 {
 ```
 
 Sample implementation of provider.
-Goal is to provide types for filed references assigned in setUp method if containing class is PHPUnit one.
-Since during 'getType' call it's impossible to access indices, we will encode all needed information and use it in 'complete' method where indices access is allowed.
+The goal is to provide types for filed references assigned in `setUp` method if containing class is PHPUnit one.
+Since during `getType` call it's impossible to access indices, we will encode all needed information and use it in 'complete' method where index access is allowed.
 
 ```java
 import com.intellij.openapi.project.Project;
diff --git a/topics/products/rider/rider.md b/topics/products/rider/rider.md
index 148a57fdc..d43c57ee2 100644
--- a/topics/products/rider/rider.md
+++ b/topics/products/rider/rider.md
@@ -46,7 +46,7 @@ For example, for a plugin with the following <path>plugin.xml</path> contents, t
 </idea-plugin>
 ```
 
-And the following <path>plugin.xml</path> would require to place the file under a path <path>dotnet/Extensions/Jean-Luc Picard.Enterprise/settings/templates.DotSettings</path>:
+And the following <path>plugin.xml</path> would require placing the file under <path>dotnet/Extensions/Jean-Luc Picard.Enterprise/settings/templates.DotSettings</path> path:
 
 ```xml
 <idea-plugin>
diff --git a/topics/reference_guide/frameworks_and_external_apis/xml_dom_api.md b/topics/reference_guide/frameworks_and_external_apis/xml_dom_api.md
index cad8a5970..a9993975f 100644
--- a/topics/reference_guide/frameworks_and_external_apis/xml_dom_api.md
+++ b/topics/reference_guide/frameworks_and_external_apis/xml_dom_api.md
@@ -60,7 +60,7 @@ if (document != null) {
 ```
 
 Looks awful, doesn't it? But there's a better way to do the same thing.
-You just need to extend a special interface --- [`DomElement`](upsource:///xml/dom-openapi/src/com/intellij/util/xml/DomElement.java).
+You just need to extend a special interface - [`DomElement`](upsource:///xml/dom-openapi/src/com/intellij/util/xml/DomElement.java).
 
 For example, let's create several interfaces:
 
diff --git a/topics/reference_guide/ui_themes/themes_extras.md b/topics/reference_guide/ui_themes/themes_extras.md
index b024b45da..5dd2ca8ff 100644
--- a/topics/reference_guide/ui_themes/themes_extras.md
+++ b/topics/reference_guide/ui_themes/themes_extras.md
@@ -109,14 +109,14 @@ A list of scroll bar `name` attributes is in the [High Contrast editor scheme](u
 These name attributes cannot be accessed from anywhere in the IDE UI at this time, so they must be manually added to an editor color scheme XML file.
 
 The following list explains the `usage` format of the `name` attribute, i.e. where a custom scroll bar color is applied:
-* `*.trackColor` — The scroll bar thumb moves across this area.
+* `*.trackColor` - The scroll bar thumb moves across this area.
   At this time the vertical scrollbar track color and transparency cannot be customized.
-* `*.thumbColor` — The movable rectangle that corresponds to the visible content's size.
-* `*.thumbBorderColor` — The thumb border.
-* `*.hoverTrackColor` — Same `usage` as above but for hover.
+* `*.thumbColor` - The movable rectangle that corresponds to the visible content's size.
+* `*.thumbBorderColor` - The thumb border.
+* `*.hoverTrackColor` - Same `usage` as above but for hover.
   At this time the vertical scrollbar hover track color and transparency cannot be customized.
-* `*.hoverThumbColor` — Same `usage` as above but for hover.
-* `*.hoverThumbBorderColor` — Same `usage` as above but for hover.
+* `*.hoverThumbColor` - Same `usage` as above but for hover.
+* `*.hoverThumbBorderColor` - Same `usage` as above but for hover.
 
 The `name` attribute patterns are enumerated below.
 
diff --git a/topics/tutorials/action_system/grouping_action.md b/topics/tutorials/action_system/grouping_action.md
index ac4987b14..0fa265e10 100644
--- a/topics/tutorials/action_system/grouping_action.md
+++ b/topics/tutorials/action_system/grouping_action.md
@@ -23,7 +23,7 @@ The `id` attribute must be unique, so incorporating the plugin ID or package nam
 The `popup` attribute determines whether actions in the group are placed in a submenu.
 The `icon` attribute specifies the FQN of an [`Icon`](work_with_icons_and_images.md) object to be displayed.
 No `compact` attribute is specified, which means this group will support submenus.
-See [Registering Actions in plugin.xml](basic_action_system.md#registering-actions-in-pluginxml) for more information about these attributes.
+See [](basic_action_system.md#registering-actions-in-pluginxml) for more information about these attributes.
 
 ```xml
 <group