Fixed a few xrefs

Signed-off-by: Prabha Kylasamiyer Sundara Rajan <[email protected]>

Author: Prabha Kylasamiyer Sundara Rajan

assemblies/rules-development-guide/assembly_rule-yaml-actions.adoc

@@ -19,11 +19,10 @@ endif::[]
 You can use rule actions to generate information about the source code. The rule action information can be included in a violation or used to categorize the source code.
 
 Rules can include the following types of actions:
-* `Message`: use message action to display an informative message in the static report that contains the violation triggered by the rule. See xref:yaml-message-actions_{context}[Message action] for more information.
-* `Tag`: use tags to categorize parts of the source code. For example, Backend=Java, where Backend is the key and Java is the value. See xref:yaml-tag-actions_{context}[Tag actions] for more information.
-Each rule includes either one of them or both of them. 
 
-include::topics/rules-development/yaml-rule-actions.adoc[leveloffset=+1]
+* `Message`: use message action to display an informative message in the static report that contains the violation triggered by the rule. See xref:yaml-message-actions_rule-yaml-actions[Message action] for more information.
+* `Tag`: use tags to categorize parts of the source code. For example, Backend=Java, where Backend is the key and Java is the value. See xref:yaml-tag-actions_rule-yaml-actions[Tag actions] for more information.
+Each rule includes either one of them or both of them. 
 
 include::topics/rules-development/yaml-tag-actions.adoc[leveloffset=+1]
 

docs/topics/rules-development/yaml-custom-variables.adoc

@@ -7,7 +7,7 @@
 = Custom variables
 
 [role="_abstract"]
-Provider conditions can have associated custom variables. You can use custom variables to capture relevant information from the matched line in the source code. The values of these variables are interpolated with data matched in the source code. These values can be used to generate detailed template messages in a rule's action (see xref:yaml-rule-actions_rule-yaml-actions[Message actions]). They can be added to a rule in the `customVariables` field:
+Provider conditions can have associated custom variables. You can use custom variables to capture relevant information from the matched line in the source code. The values of these variables are interpolated with data matched in the source code. These values can be used to generate detailed template messages in a rule's action (see xref:yaml-message-actions_rule-yaml-actions[Message actions]). They can be added to a rule in the `customVariables` field:
 
 [source,yaml]
 ----

docs/topics/rules-development/yaml-message-actions.adoc

@@ -7,15 +7,26 @@
 = Message action
 
 [role="_abstract"]
-A message action is employed to generate an issue with the specified message when a rule matches, for example:
+A message action is used to generate an issue with the specified message when a rule condition matches the source code, for example:
 
 [source,yaml]
 ----
-# When a match is found, the analyzer generates incidents with the same message.
-message: "helpful message about the violation"
+- ruleID: test-rule
+  message: Test rule matched. Please resolve this migration issue.
+  when:
+    <CONDITION>
+----
+
+Optionally, a message can include hyperlinks to external URLs that provide relevant information about the issue or a quick fix.
+
+[source,yaml]
+----
+links:
+  - url: "konveyor.io"
+    title: "Short title for the link"
 ----
 
-You can also create a template message to include information about the match that has been interpolated through custom variables on the rule.
+You can also create a template message to include information about the match that has been interpolated through xref:yaml-custom-variables_logical-chaining-custom-variables[custom variables] on the rule.
 // link link:#custom-variables[Custom Variables]):
 
 [source,yaml]