Update README.md, add and fix links in PGD docs

Minor improvements  to `README.md`.
Add link to the OpenTelemetry project in the OpenTelemetry chapter.
Fix broken links in the Monitoring through SQL chapter.

Signed-off-by: Lenz Grimmer <[email protected]>

README.md

@@ -45,7 +45,7 @@ At this point you have a couple options.
 
 1. Run `npm run start`. The application will start in the background and take a few minutes to load.
 
-1. You can view logs and monitor the startup process by running `npm run logs`. Once it's finished it can be accessed at `http://localhost:8000/`.
+1. You can view logs and monitor the startup process by running `npm run logs`. Once it's finished it can be accessed at [http://localhost:8000/](http://localhost:8000).
 
 #### Additional Commands and Options for the Docker Environment
 
@@ -63,7 +63,7 @@ At this point you have a couple options.
 
 If you find that the container crashes frequently or see that your container has exited with code 137, increasing the Docker memory should help. Allocating at least 4GB is recommended.
 
-1. open Docker Desktop
+1. Open Docker Desktop
 
 1. Go to Preferences (gear icon in the top right corner)
 
@@ -283,7 +283,7 @@ If you need to setup a redirect from Docs 1.0 to Docs 2.0 manually, this is the
 
 # MDX Format
 
-Documentation must be formatted as an [MDX file](https://www.gatsbyjs.com/docs/mdx/writing-pages/) with the `.mdx` extension. MDX is a superset of [Markdown](https://www.markdownguide.org/).
+Documentation must be formatted as an [MDX file](https://www.gatsbyjs.com/docs/how-to/routing/mdx/) with the `.mdx` extension. MDX is a superset of [Markdown](https://www.markdownguide.org/). See [What is MDX?](https://mdxjs.com/docs/what-is-mdx/) for a detailed explanation of the format.
 
 ## Frontmatter
 

product_docs/docs/pgd/5/monitoring/otel.mdx

@@ -3,7 +3,7 @@ title: OpenTelemetry integration
 ---
 
 You can configure EDB Postgres Distributed to report monitoring information
-as well as traces to the OpenTelemetry collector.
+as well as traces to the [OpenTelemetry](https://opentelemetry.io/) collector.
 
 EDB Postgres Distributed OTEL collector fills several resource attributes.
 These are attached to all metrics and traces:

product_docs/docs/pgd/5/monitoring/sql.mdx

@@ -113,7 +113,7 @@ You can use another view for monitoring of outgoing replication activity:
 
 -   [`bdr.node_replication_rates`](/pgd/latest/reference/catalogs-visible/#bdrnode_replication_rates) for monitoring outgoing replication
 
-The []`bdr.node_replication_rates`](/pgd/latest/reference/catalogs-visible/#bdrnode_replication_rates) view gives an overall picture of the outgoing
+The [`bdr.node_replication_rates`](/pgd/latest/reference/catalogs-visible/#bdrnode_replication_rates) view gives an overall picture of the outgoing
 replication activity along with the catchup estimates for peer nodes,
 specifically.
 
@@ -152,7 +152,7 @@ view.
 !!! Note
     This catalog is present only when the bdr-enterprise extension is installed.
 
-Administrators can query `[`bdr.node_slots`](/pgd/latest/reference/catalogs-visible/#bdrnode_slots) for outgoing replication from the
+Administrators can query [`bdr.node_slots`](/pgd/latest/reference/catalogs-visible/#bdrnode_slots) for outgoing replication from the
 local node. It shows information about replication status of all other nodes
 in the group that are known to the current node as well as any additional
 replication slots created by PGD on the current node.