chore: improve docs and scripts consistency

- Update issue template formatting for clarity and consistency.
- Use italics instead of bold for notes in README for better style.
- Enhance npm scripts to run Prettier with lint/fix commands.
- Remove unnecessary blank line in GitHub Actions workflow.

Author: dansomething

.github/ISSUE_TEMPLATE/issue-report.md

@@ -4,14 +4,14 @@ about: Create a report to help us improve
 title: ''
 labels: ''
 assignees: ''
-
 ---
 
 **Describe the issue**
 A clear and concise description of the problem.
 
 **To Reproduce**
 Steps to reproduce the behavior:
+
 1. Go to '...'
 2. Open this file '....'
 3. Run this command '....'
@@ -21,21 +21,23 @@ Steps to reproduce the behavior:
 A clear and concise description of what you expected to happen.
 
 **Versions of relevant software**
- - vim:
- - coc.nvim:
- - coc-java:
- - vimspector:
- - java:
- - maven:
+
+- vim:
+- coc.nvim:
+- coc-java:
+- vimspector:
+- java:
+- maven:
 
 **Relevant logs and error messages**
-* View the trace logging output for the Java language server:
-    * Set `{ "java.trace.server": "verbose" }` in `:CocSettings`.
-    * Run the command `:CocCommand workspace.showOutput java`.
-    * Are there any errors?
-* View the Vimspector log `:VimspectorShowOutput Vimspector`.
-    * Are the any errors?
-* After running the command `:CocCommand java.debug.vimspector.start` Do you see a message like `[coc.nvim] Java debug server started on port` in the output of `:messages`?
+
+- View the trace logging output for the Java language server:
+  - Set `{ "java.trace.server": "verbose" }` in `:CocSettings`.
+  - Run the command `:CocCommand workspace.showOutput java`.
+  - Are there any errors?
+- View the Vimspector log `:VimspectorShowOutput Vimspector`.
+  - Are the any errors?
+- After running the command `:CocCommand java.debug.vimspector.start` Do you see a message like `[coc.nvim] Java debug server started on port` in the output of `:messages`?
 
 **Additional context**
 Add any other context about the problem here.

.github/workflows/node.js.yml

@@ -10,7 +10,6 @@ on:
 
 jobs:
   build:
-
     runs-on: ubuntu-latest
 
     strategy:

README.md

@@ -213,13 +213,13 @@ Add the following contents to the `.vimspector.json` file in the root directory
 }
 ```
 
-*Review the [Vimspector config][12] docs for what's possible within this file.*
+_Review the [Vimspector config][12] docs for what's possible within this file._
 
 ##### Configure Vim
 
 This extension provides `:CocCommand java.debug.vimspector.start` to simplify launching Vimspector.
 
-*Note, it does not start your Java process in remote debug mode. An example of how to do that is covered below.*
+_Note, it does not start your Java process in remote debug mode. An example of how to do that is covered below._
 
 To further simplify, launching Vimspector, add the following config to your `~/.vimrc` file or wherever appropriate for
 your Vim setup.
@@ -263,11 +263,11 @@ the breakpoint you set.
 
 That's it! You may now [step debug][20] your way through a Java program from within Vim.
 
-*Note, if you use a Java debug port different than `5005` you will need to change that value in your `.vimspector.json`
+_Note, if you use a Java debug port different than `5005` you will need to change that value in your `.vimspector.json`
 file. It is also possible to configure this port dynamically in Vimspector in the same manner as the debug adapter
-port.*
+port._
 
-*Also note, if you use Maven for builds you may start [remote debugging][14] for tests and then run Vimspector.*
+_Also note, if you use Maven for builds you may start [remote debugging][14] for tests and then run Vimspector._
 
 ```sh
 mvn test -Dmaven.surefire.debug
@@ -278,7 +278,7 @@ mvn test -Dmaven.surefire.debug
 If you'd prefer to launch the Vimspector plugin directly with your own configuration then add something similar the
 following config to your `~/.vimrc` file or wherever appropriate for your Vim setup.
 
-*Note, this will bypass using the `:CocCommand` documented above to start the debug session.*
+_Note, this will bypass using the `:CocCommand` documented above to start the debug session._
 
 ```viml
 function! JavaStartDebugCallback(err, port)

package.json

@@ -31,8 +31,8 @@
   "scripts": {
     "build": "node esbuild.mjs",
     "clean": "rimraf lib",
-    "fix": "eslint --fix .",
-    "lint": "eslint .",
+    "fix": "eslint --fix && prettier --write .",
+    "lint": "eslint && prettier --check .",
     "prepare": "npm-run-all clean build",
     "release": "np --no-tests",
     "watch": "node esbuild.mjs --watch"