Merge pull request #2616 from prometheus/fionaliao-patch-1

Small fixes to utf-8 and opentelemetry guides

Author: fionaliao

content/docs/guides/opentelemetry.md

@@ -83,7 +83,7 @@ there are certain worth attaching to all your OTLP metrics.
 
 By default, Prometheus won't be promoting any attributes. If you'd like to promote any
 of them, you can do so in this section of the Prometheus configuration file. The following
-snippet shares the best practise set of attributes to promote:
+snippet shares the best practice set of attributes to promote:
 
 ```yaml
 otlp:

content/docs/guides/utf8.md

@@ -16,7 +16,7 @@ This document guides you through the UTF-8 transition details.
 
 # Go Instrumentation 
 
-Currently, metrics created by the official Prometheus [client_golang library](github.com/prometheus/client_golang) will reject UTF-8 names
+Currently, metrics created by the official Prometheus [client_golang library](https://github.com/prometheus/client_golang) will reject UTF-8 names
 by default. It is necessary to change the default validation scheme to allow
 UTF-8. The requirement to set this value will be removed in a future version of
 the common library.
@@ -97,7 +97,7 @@ OTLP receiver in Prometheus 3.0 still normalizes all names to Prometheus format
       translation_strategy: NoUTF8EscapingWithSuffixes
 
 
-See [OpenTelemetry guide](./opentelemetry) for more details.
+See [OpenTelemetry guide](/docs/guides/opentelemetry) for more details.
 
 
 # Querying
@@ -119,4 +119,4 @@ Label names must also be quoted if they contain legacy-incompatible characters:
 `{"metric.name", "my.label.name"="bar"}`
 
 The metric name can appear anywhere inside the braces, but style prefers that it
-be the first term.
+be the first term.