fix some link to html instead of md documents

.idea/composerJson.xml

@@ -0,0 +1,9 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<project version="4">
+  <component name="ComposerJsonPluginSettings">
+    <unboundedVersionInspectionSettings>
+      <excludedPackages />
+    </unboundedVersionInspectionSettings>
+    <customRepositories />
+  </component>
+</project>

basics/architectural_overview/file_view_providers.md

@@ -23,7 +23,7 @@ A `FileViewProvider` instance corresponds to a single `VirtualFile`, a single `D
 
 ## How do I extend the FileViewProvider?
 
-To create a file type that has multiple interspersing trees for different languages, your plugin must contain an extension to the `fileType.fileViewProviderFactory` [extension point](/basics/plugin_structure/plugin_extensions_and_extension_points.html) available in the *IntelliJ Platform* core.
+To create a file type that has multiple interspersing trees for different languages, your plugin must contain an extension to the `fileType.fileViewProviderFactory` [extension point](/basics/plugin_structure/plugin_extensions_and_extension_points.md) available in the *IntelliJ Platform* core.
 
 This extension point is declared using the [FileTypeExtensionPoint](upsource:///platform/core-api/src/com/intellij/openapi/fileTypes/FileTypeExtensionPoint.java)
 bean class.

basics/plugin_structure/plugin_content.md

@@ -6,9 +6,9 @@ There are two possible ways of organizing plugin content:
 
 1. A plugin consisting of one `.jar` file placed in the plugins directory:
 
-   The archive should contain the configuration file (`META-INF/plugin.xml`) and classes that implement the plugin functionality. The configuration file specifies the plugin name, description, version, vendor, the supported IntelliJ IDEA version, plugin components, actions and action groups, and action user interface placement.
+    The archive should contain the configuration file (`META-INF/plugin.xml`) and classes that implement the plugin functionality. The configuration file specifies the plugin name, description, version, vendor, the supported IntelliJ IDEA version, plugin components, actions and action groups, and action user interface placement.
 
-   ```
+    ```
 .IntelliJIDEAx0
     plugins
         sample.jar/
@@ -17,12 +17,12 @@ There are two possible ways of organizing plugin content:
             ...
             META-INF
                 plugin.xml
-   ```
+```
    
 
 2. Plugin files located in a `.jar` file that is placed in the lib folder:
 
-   ```
+    ```
 .IntelliJIDEAx0
     plugins
         Sample
@@ -32,9 +32,9 @@ There are two possible ways of organizing plugin content:
                 Sample.jar/
                     com/foo/...
                     ...
-					...
-					META-INF
-						plugin.xml
-   ```
+                    ...
+                    META-INF
+                        plugin.xml
+    ```
 
    All jars from the `lib` folder are automatically added to the classpath.

basics/plugin_structure/plugin_extensions_and_extension_points.md

@@ -10,7 +10,7 @@ If you want your plugin to allow other plugins to extend its functionality, in t
 
 ## Extensions
 
-If you want your plugin to extend the functionality of other plugins or the *IntelliJ Platform*, you must declare one or several _extensions_.
+If you want your plugin to extend the functionality of other plugins or the *Intell           iJ Platform*, you must declare one or several _extensions_.
 
 ## How to declare extensions and extension points
 

basics/project_structure.md

@@ -16,7 +16,7 @@ In the *IntelliJ Platform*, a _project_ encapsulates all your source code, libra
 
 ### Module
 
-A _module_ is a discrete unit of functionality that can be run, tested, and debugged independently. Modules includes such things as source code, build scripts, unit tests, deployment descriptors, etc. In the project, each module can use a specific SDK or inherit SDK defined on the project level (see the [SDK](/reference_guide/project_model/sdk.html) section later in this document). A module can depend on other modules of the project.
+A _module_ is a discrete unit of functionality that can be run, tested, and debugged independently. Modules includes such things as source code, build scripts, unit tests, deployment descriptors, etc. In the project, each module can use a specific SDK or inherit SDK defined on the project level (see the [SDK](/reference_guide/project_model/sdk.md) section later in this document). A module can depend on other modules of the project.
 
 ### Library
 

basics/virtual_file_system.md

@@ -40,7 +40,7 @@ During the lifetime of a running instance of an IntelliJ Platform IDE, multiple
 
 From the point of view of the caller, refresh operations can be either synchronous or asynchronous. In fact, the refresh operations are executed according to their own threading policy, and the synchronous flag simply means that the calling thread will be blocked until the refresh operation (which will most likely run on a different thread) is completed.
 
-Both synchronous and asynchronous refreshes can be initiated from any thread. If a refresh is initiated from a background thread, the calling thread must not hold a read action, because otherwise a deadlock would occur. See [IntelliJ Platform Architectural Overview](/basics/architectural_overview/general_threading_rules.html) for more details on the threading model and read/write actions.
+Both synchronous and asynchronous refreshes can be initiated from any thread. If a refresh is initiated from a background thread, the calling thread must not hold a read action, because otherwise a deadlock would occur. See [IntelliJ Platform Architectural Overview](/basics/architectural_overview/general_threading_rules.md) for more details on the threading model and read/write actions.
 
 The same threading requirements also apply to functions like [LocalFileSystem.refreshAndFindFileByPath()](upsource:///platform/platform-api/src/com/intellij/openapi/vfs/LocalFileSystem.java), which perform a partial refresh if the file with the specified path is not found in the snapshot.
 

tutorials/editor_basics/editor_events.md

@@ -85,7 +85,7 @@ Create an action:
 
 ```java
 public class EditorHandlerIllustration extends AnAction {
-    @Override
+    @Override                                        
     public void actionPerformed(@NotNull AnActionEvent anActionEvent) {
     }
     @Override