fix readme

Author: hadarauelena

.github/scripts/README.md

@@ -124,6 +124,7 @@ These rules can be found in the [HDL coding guidelines](https://analogdevicesinc
 It checks if the license header is up-to-date, containing the current year in
 the year range. Exceptions are the JESD files and the ones specified in the
 `avoid_list` string list.
+
 If `-e` option is added, the script can update the year range.
 
 #### 2. Empty lines
@@ -132,18 +133,21 @@ It checks if the file contains empty line issues:
 * Two or more consecutive empty lines.
 * An empty line at the beginning of the file.
 * An empty line at the end of the file.
-If the `-e` option is added, the script removes redundant empty lines and ensures
+
+If `-e` option is added, the script removes redundant empty lines and ensures
 that at most one empty line is kept, while also removing any leading or trailing
 empty lines.
 
 #### 3. Trailing whitespace
 
 It checks if there are whitespace characters at the end of the lines.
+
 If `-e` option is added, then they can be removed.
 
 #### 4. Lines after end token
 
 It checks if there are lines after end token (`endmodule` or `endpackage`).
+
 If `-e` option is added, the script can remove them.
 
 #### 5. Parentheses around the module declaration
@@ -152,6 +156,7 @@ It checks if the parentheses around the module declaration (meaning `) (` for
 the parameters' list) are on an empty line, right after the last parameter.
 It also checks for the closing parenthesis at the module declaration (meaning `);`)
 to be on an empty line, at the beginning, right after the last I/O port line.
+
 If `-e` option is added, the script can put them in their proper place.
 
 #### 6. Indentation of code
@@ -175,8 +180,8 @@ It checks if SystemVerilog packages are defined correctly:
 * `package <name>;` starts at column 0, with no extra spaces before or after ;.
 * `endpackage` is alone on its line at column 0.
 * Exactly one newline follows `endpackage`.
-* Inside the package, typedefs and localparams follow the same indentation and
-alignment rules.
+* Inside the package, typedefs and localparams follow the same indentation and alignment rules.
+
 If the `-e` option is added, the script rewrites these to the guideline-compliant
 format.
 
@@ -191,6 +196,7 @@ item has no comma.
   * Following elements are indented +2 spaces.
   * Inline comments are aligned at least 4 spaces after the longest element.
   * The closing `};` is attached to the last element.
+
 If the `-e` option is added, the script normalizes the block automatically.
 
 #### 10. Typedefs
@@ -201,6 +207,7 @@ It checks if typedef blocks are formatted correctly:
 * Inner items are indented +2.
 * Closing `} type_name;` is aligned with the opening `typedef`.
 * Inline comments after the closing are moved to a separate line.
+
 If the `-e` option is added, the script rewrites the block to the guideline-compliant
 format.