diff --git a/topics/tutorials/code_inspections.md b/topics/tutorials/code_inspections.md
index 2cedf92f6..af4ef80ce 100644
--- a/topics/tutorials/code_inspections.md
+++ b/topics/tutorials/code_inspections.md
@@ -9,7 +9,7 @@ In addition, the comparing_references_inspection code sample demonstrates implem
You can also create custom inspections through the IntelliJ IDEA user interface.
See [Code Inspection](https://www.jetbrains.com/idea/webhelp/code-inspection.html) and [Creating Custom Inspections](https://www.jetbrains.com/idea/help/creating-custom-inspections.html) for more information.
-
+
See [Inspections](https://jetbrains.design/intellij/text/inspections/) topic in the IntelliJ Platform UI Guidelines on naming, writing description, and message texts for inspections.
## Creating an Inspection Plugin
@@ -156,7 +156,7 @@ You can specify the Java classes to participate in the code inspection and the s
On the main menu, open the Settings/Preferences | Editor | Inspections dialog.
In the list of the IntelliJ IDEA Java inspections, expand the Probable bugs node, and then click SDK: '==' or '!=' instead of 'equals()'.
-
+
Under Options, you can specify the following plugin settings:
* From the Severity list, select the severity level of probable bugs the plugin finds such as Warning, Error, etc.
@@ -168,7 +168,7 @@ Under Options, you can specify the following plugin settings:
The plugin inspects your code opened in the IntelliJ IDEA editor.
The plugin highlights the code fragments where two variables of the reference type are separated by `==` or `!=` and proposes to replace this code fragment with `.equals()`:
-
+
In this example, the `str1` and `str2` are variables of the String type.
Clicking SDK: Use equals() replaces:
diff --git a/topics/tutorials/code_intentions.md b/topics/tutorials/code_intentions.md
index 4444614a0..aa467746b 100644
--- a/topics/tutorials/code_intentions.md
+++ b/topics/tutorials/code_intentions.md
@@ -10,7 +10,7 @@ In addition, the sample plugin contains a JUnit-based test.
The IntelliJ Platform analyzes your code and helps handle situations that may result in errors.
When a possible problem is suspected, the IDE suggests an appropriate intention action, denoted with special icons.
For more information, refer to [Intention Actions](https://www.jetbrains.com/help/idea/intention-actions.html) in the IntelliJ IDEA Web Help.
-
+
See [Inspections](https://jetbrains.design/intellij/text/inspections/) topic in the IntelliJ Platform UI Guidelines on naming, writing description, and message texts for inspections/intentions.
You can view a list of all available intention actions as well as enable/disable them using the [Intentions List](https://www.jetbrains.com/help/idea/intention-actions.html#intention-settings) in Settings/Preferences | Editor | Intentions.
@@ -28,7 +28,7 @@ The [conditional_operator_intention](https://github.com/JetBrains/intellij-sdk-c
When launched, this plugin adds the Convert ternary operator if statement item to the Conditional Operator node in the Intentions List:
-
+
#### Running the Plugin
@@ -39,7 +39,7 @@ See [Code Samples](code_samples.md) on how to set up and run the plugin.
The plugin analyzes symbols under the cursor in your code opened in the editor.
If the cursor is positioned on the `?` conditional operator, IntelliJ IDEA proposes to replace this conditional (ternary) operator with the "if-then-else" statement:
-
+
In this example, the code: