diff --git a/topics/basics/testing_plugins/writing_tests.md b/topics/basics/testing_plugins/writing_tests.md
index f98913c8b..25cb653ff 100644
--- a/topics/basics/testing_plugins/writing_tests.md
+++ b/topics/basics/testing_plugins/writing_tests.md
@@ -1,6 +1,8 @@
-[//]: # (title: Writing Tests)
+<!-- Copyright 2000-2023 JetBrains s.r.o. and contributors. Use of this source code is governed by the Apache 2.0 license. -->
 
-<!-- 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. -->
+# Writing Tests
+
+<link-summary>Introduction to implementing tests.</link-summary>
 
 In most cases, once you have the necessary files copied to the test project and loaded into the in-memory editor, writing the test itself involves invoking your plugin code and has few dependencies on the test framework.
 
@@ -16,4 +18,4 @@ To compare the results of executing the action with the expected results, you ca
 The file with the expected results can also contain [markup](test_project_and_testdata_directories.md#special-markup) to specify the expected caret position or selected text range.
 Suppose you're testing an action that modifies multiple files (a project-wide refactoring, for example). In that case, you can compare an entire directory under the test project with the expected output using `PlatformTestUtil.assertDirectoriesEqual()`.
 
-See [Useful Classes](testing_faq.md#useful-classes) for other common testing functionality.
\ No newline at end of file
+See [Useful Classes](testing_faq.md#useful-classes) for other common testing functionality.