Merge pull request #115 from KotlinFoundation/fix-issue-tracker-link

fix: proper link to issue tracker

Author: berezinant

src/pages/submitting-incompatible-changes.mdx

@@ -4,7 +4,7 @@ title: "Guide to submitting incompatible changes"
 
 # Guide to submitting incompatible changes
 
-A proposal is usually written by a developer responsible for the change or the relevant subsystems. It has to be described in the [issue tracker](https://youtrack.jetbrains.com/issues/KT?q=%23for-language-committee%20%23Unresolved%20tag:%20-language-committee-approved) and marked with the "for-language-committee" tag. To provide all the necessary details, issue in the tracker should follow the template below.
+A proposal is usually written by a developer responsible for the change or the relevant subsystems. It has to be described in the [issue tracker](https://youtrack.jetbrains.com/issues/KTLC) and marked with the "for-language-committee" tag. To provide all the necessary details, issue in the tracker should follow the template below.
 
 ## Issue template
 
@@ -25,15 +25,15 @@ Detection and Migration modes: <see guide below>
 > 2. What's wrong with it
 > 3. Detailed explanation of why and how this happens
 > 4. Any known reasoning behind such behavior
-> 5. Affected versions: when did the problem appear first? 
+> 5. Affected versions: when did the problem appear first?
 
 # Proposed changes
 > 1. Proposed changes
 > 2. How it fixes the issue?
 
 # Impact
 > Examples of negative effects: changes of behavior, previously compiled code forbidden, etc.
-> If possible: 
+> If possible:
 > * number of impacted users
 > * how common this pattern is
 > * if we believe it's a rare case, why
@@ -47,7 +47,7 @@ Detection and Migration modes: <see guide below>
 ## Classification
 
 The **Classification** section needs to classify the change, without describing its essence.
-The classification is used by the Committee to quickly assess the severity of the issue. Here are the common categories to be used. 
+The classification is used by the Committee to quickly assess the severity of the issue. Here are the common categories to be used.
 
 This section can be used as a checklist of things that need to be evaluated/thought of.
 
@@ -61,7 +61,7 @@ Specify one or more of the following:
         *   Affecting ABI
         *   Not affecting ABI
     *   API moved to different artifact
-    *   API type signature change 
+    *   API type signature change
         *   Affecting ABI
         *   Not affecting ABI
     *   Contract refinement