Merge remote-tracking branch 'origin/main' into arve/info-blog-post

Author: aknuds1

docs/instrumenting/writing_clientlibs.md

@@ -244,7 +244,7 @@ aspects](/docs/practices/instrumentation/#use-labels) of Prometheus, but
 Accordingly client libraries must be very careful in how labels are offered to
 users.
 
-Client libraries MUST NOT allow users to have different
+Client libraries SHOULD NOT allow users to have different
 label names for the same metric for Gauge/Counter/Summary/Histogram or any
 other Collector offered by the library.
 

docs/specs/om/open_metrics_spec_2_0.md

@@ -108,7 +108,7 @@ Each MetricPoint consists of a set of values, depending on the MetricFamily type
 
 Exemplars are references to data outside of the MetricSet. A common use case are IDs of program traces.
 
-Exemplars MUST consist of a LabelSet and a value, and MAY have a timestamp. They MAY each be different from the MetricPoints' LabelSet and timestamp.
+Exemplars MUST consist of a LabelSet and a value, and SHOULD have a timestamp. They MAY each be different from the MetricPoints' LabelSet and timestamp.
 
 The combined length of the label names and values of an Exemplar's LabelSet MUST NOT exceed 128 UTF-8 character code points. Other characters in the text rendering of an exemplar such as `",=` are not included in this limit for implementation simplicity and for consistency between the text and proto formats.