diff --git a/topics/tutorials/code_documentation.md b/topics/tutorials/code_documentation.md
index 9221003c8..44e382cc1 100644
--- a/topics/tutorials/code_documentation.md
+++ b/topics/tutorials/code_documentation.md
@@ -1,4 +1,4 @@
-[//]: # (title: Documentation)
+# Documentation
 
 <!-- Copyright 2000-2022 JetBrains s.r.o. and other contributors. Use of this source code is governed by the Apache 2.0 license that can be found in the LICENSE file. -->
 
@@ -8,6 +8,8 @@
 
 </tldr>
 
+<link-summary>Documentation for code elements inside the editor.</link-summary>
+
 Quick Documentation helps users by showing documentation, e.g., for classes, functions, or methods inside the editor.
 Plugin authors implement
 [`DocumentationProvider`](%gh-ic%/platform/analysis-api/src/com/intellij/lang/documentation/DocumentationProvider.java)
diff --git a/topics/tutorials/code_inspections.md b/topics/tutorials/code_inspections.md
index 58a683aac..6edcf2728 100644
--- a/topics/tutorials/code_inspections.md
+++ b/topics/tutorials/code_inspections.md
@@ -1,4 +1,4 @@
-[//]: # (title: Code Inspections)
+# Code Inspections
 
 <!-- Copyright 2000-2022 JetBrains s.r.o. and other contributors. Use of this source code is governed by the Apache 2.0 license that can be found in the LICENSE file. -->
 
@@ -8,6 +8,8 @@
 
 </tldr>
 
+<link-summary>Tutorial: implementing Inspections to highlight code in the editor.</link-summary>
+
 The IntelliJ Platform provides tools designed for static code analysis called _code inspections_, which help the user maintain and clean up code without actually executing it.
 Custom code inspections can be implemented as IntelliJ Platform plugins.
 Examples of the plugin approach are the IntelliJ Platform SDK code samples [inspection_basics](%gh-sdk-samples%/inspection_basics) and [comparing_references_inspection](%gh-sdk-samples%/comparing_references_inspection).
diff --git a/topics/tutorials/controlling_highlighting.md b/topics/tutorials/controlling_highlighting.md
index 545e07eca..ee5dc40b6 100644
--- a/topics/tutorials/controlling_highlighting.md
+++ b/topics/tutorials/controlling_highlighting.md
@@ -1,7 +1,9 @@
-[//]: # (title: Controlling Highlighting)
+# Controlling Highlighting
 
 <!-- Copyright 2000-2022 JetBrains s.r.o. and other contributors. Use of this source code is governed by the Apache 2.0 license that can be found in the LICENSE file. -->
 
+<link-summary>Suppressing highlighting in the editor programmatically.</link-summary>
+
 The results of analyzing code by several mechanisms provided by the IntelliJ Platform ([Syntax errors](syntax_errors.md), Annotators, [Inspections](code_inspections.md)) are converted to highlighting information used to highlight the code in the editor.
 However, in some contexts, the provided highlighting information is invalid or unnecessary.
 
diff --git a/topics/tutorials/syntax_errors.md b/topics/tutorials/syntax_errors.md
index 09e26c36f..5aa11b05a 100644
--- a/topics/tutorials/syntax_errors.md
+++ b/topics/tutorials/syntax_errors.md
@@ -1,7 +1,9 @@
-[//]: # (title: Syntax Errors)
+# Syntax Errors
 
 <!-- Copyright 2000-2022 JetBrains s.r.o. and other contributors. Use of this source code is governed by the Apache 2.0 license that can be found in the LICENSE file. -->
 
+<link-summary>Suppressing syntax errors in the editor programmatically.</link-summary>
+
 The IntelliJ Platform provides a mechanism for analyzing the PSI tree and highlighting syntax errors out of the box.
 
 While the PSI tree for the code is being built, a [parser](implementing_parser_and_psi.md) tries to consume tokens according to language grammar.