Improve readme file configuration instructions

Author: pmoura

README.md

@@ -187,12 +187,12 @@ No defaults (VSCode doesn't support using environment variables to define settin
     "logtalk.executable.path": "/usr/local/bin/logtalk"
     "logtalk.executable.arguments": [ ]
 
-Logtalk executable or integration script plus its arguments. The `logtalk` executable can be created by running the `logtalk_backend_select` script. In alternative, use the integration script you want to use. Absolute paths **must** be used. For example, assuming a POSIX system (e.g. macOS, Linux, or BSD):
+Logtalk executable or integration script plus its arguments. On POSIX systems (e.g. macOS, Linux, or BSD), the `logtalk` executable can be created by running the `logtalk_backend_select` script. In alternative, use the integration script you want to use. Absolute paths **must** be used. For example, assuming a POSIX system and using SWI-Prolog as the backend:
 
     "logtalk.executable.path": "/usr/local/bin/swilgt"
     "logtalk.executable.arguments": [ "-q" ]
 
-On Windows systems, use the absolute path to the Prolog backend executable **and** then set the arguments to load Logtalk (look into the properties of the Logtalk integration shortcuts that are available from the Start Menu after installing Logtalk). For example (assuming the default Logtalk installation):
+On Windows systems, use the absolute path to the Prolog backend executable **and** then set the arguments to load Logtalk (look into the properties of the Logtalk integration shortcuts that are available from the Start Menu after installing Logtalk). For example (assuming the default Logtalk installation) and using SWI-Prolog as the backend:
 
     "logtalk.executable.path": "C:/Program Files/swipl/bin/swipl.exe"
     "logtalk.executable.arguments": [
@@ -205,12 +205,12 @@ On Windows systems, use the absolute path to the Prolog backend executable **and
     "logtalk.tester.script": "/usr/local/bin/logtalk_tester"
     "logtalk.tester.arguments": [ ]
 
-Automation script for running tests and its arguments. The arguments **must** included at least the Prolog backend. For example, assuming a POSIX system (e.g. macOS, Linux, or BSD):
+Automation script for running tests and its arguments. The arguments **must** included at least the Prolog backend. For example, assuming a POSIX system (e.g. macOS, Linux, or BSD) and using SWI-Prolog as the backend:
 
     "logtalk.tester.script": "/usr/local/bin/logtalk_tester"
     "logtalk.tester.arguments": [ "-p", "swi" ]
 
- On Windows systems, these settings must be set differently. For example (assuming the default Logtalk installation):
+On Windows systems, these settings must be set differently. For example (assuming the default Logtalk installation) and using SWI-Prolog as the backend:
 
     "logtalk.tester.script": "C:/Program Files/PowerShell/7/pwsh.exe"
     "logtalk.tester.arguments": [
@@ -222,12 +222,12 @@ Automation script for running tests and its arguments. The arguments **must** in
     "logtalk.doclet.script": "/usr/local/bin/logtalk_doclet"
     "logtalk.doclet.arguments": [ ]
 
-Automation script for running doclets and its arguments. The arguments **must** included at least the Prolog backend. For example, assuming a POSIX system (e.g. macOS, Linux, or BSD):
+Automation script for running doclets and its arguments. The arguments **must** included at least the Prolog backend. For example, assuming a POSIX system (e.g. macOS, Linux, or BSD) and using SWI-Prolog as the backend:
 
     "logtalk.doclet.script": "/usr/local/bin/logtalk_doclet"
     "logtalk.doclet.arguments": [ "-p", "swi" ]
 
-On Windows systems, these settings must be set differently. For example (assuming the default Logtalk installation):
+On Windows systems, these settings must be set differently. For example (assuming the default Logtalk installation) and using SWI-Prolog as the backend:
 
     "logtalk.doclet.script": "C:/Program Files/PowerShell/7/pwsh.exe"
     "logtalk.doclet.arguments": [
@@ -269,7 +269,7 @@ Diagrams script for converting the `.dot` files generated by the Logtalk `diagra
 
     "logtalk.scripts.timeout": 480000
 
-The number of milliseconds to wait before running the scripts that convert `.xml` documentation files and `.dot` diagram files to final formats when running the `lgtdoc` and `diagrams` tools. This timeout is also used to wait for a file compilation to finish before adding any compiler errors or warnings to the "Problems" pane. You may need to set a value larger than the default value if you're compiling big applications.
+The number of milliseconds to wait before running the scripts that convert `.xml` documentation files and `.dot` diagram files to final formats when running the `lgtdoc` and `diagrams` tools. This timeout is also used to wait for a file compilation to finish before adding any compiler errors or warnings to the "Problems" pane and for waiting to answers from the Logtalk reflection API when using code navigation features. You may need to set a value larger than the default value if you're compiling big applications.
 
 ## Known Issues