Made minor formatting changes

Signed-off-by: Prabha Kylasamiyer Sundara Rajan <pkylasam@pkylasam-thinkpadp16vgen1.bengluru.csb>

Author: Prabha Kylasamiyer Sundara Rajan

docs/topics/rules-development/create-go-custom-rule.adoc

@@ -9,7 +9,7 @@
 [role="_abstract"]
 You can create custom rules for Golang (Go) applications based on the following example.
 
-You can use the following custom rule to check if {ProductShortName} triggers an incident when it detects the `v1beta1.CustomResourceDefinition` in the`go` file.
+You can use the following custom rule to check if {ProductShortName} triggers an incident when it detects the `v1beta1.CustomResourceDefinition` in the `go` file.
 
 .Procedure
 . Create a `go-rule-001.yml` file in a directory. 

docs/topics/rules-development/create-nodejs-custom-rule.adoc

@@ -7,7 +7,7 @@
 = Creating a custom Node.js rule
 
 [role="_abstract"]
- You must create custom rules to analyze `Node.js` applications by using {ProductShortName}. A `Node.js` rule can contain the `nodejs.referenced` capability which supports the `pattern` field. 
+You must create custom rules to analyze `Node.js` applications by using {ProductShortName}. A `Node.js` rule can contain the `nodejs.referenced` capability which supports the `pattern` field. 
 
 The following example uses a custom rule to check if a `.tsx` file in the `Node.js` project imports the `React` framework.
 

docs/topics/rules-development/yaml-chaining-condition-variables.adoc

@@ -10,8 +10,6 @@
 You can use the output of one condition as the input for filtering another one in the `and` and `or` conditions. This is called *condition chaining*.
 
 
-.Example
-
 [source,yaml]
 ----
 when:
@@ -28,7 +26,6 @@ when:
 
 In the above example, the output of the `builtin.file` condition is saved as `poms`:
 
-+
 [source,yaml]
 ----
 [...]
@@ -40,7 +37,6 @@ The variables of `builtin.file` can then be used in the `builtin.xml` condition,
 
 This is how this particular condition knows how to use the variable set to the name `poms`.
 
-+
 [source,yaml]
 ----
 [...]
@@ -51,7 +47,6 @@ This is how this particular condition knows how to use the variable set to the n
 Then you can use the variables by setting them as mustached templates in
 any of the inputs to the _provider_ condition.
 
-+
 [source,yaml]
 ----
 [...]
@@ -64,7 +59,7 @@ any of the inputs to the _provider_ condition.
 If you only want to use the values of a condition as a chain, you can set `ignore: true`.
 
 This will tell the engine not to use this condition to determine whether the rule has been violated or not:
-+
+
 [source,yaml]
 ----
 [...]