From 7bd88e31a68af2fa1f889288fea35f0eaa564189 Mon Sep 17 00:00:00 2001
From: jtl-novatec <151550827+jtl-novatec@users.noreply.github.com>
Date: Wed, 17 Apr 2024 13:20:52 +0200
Subject: [PATCH] Update index.md

---
 tutorial/content/labs/instrumentation/manual/metrics/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tutorial/content/labs/instrumentation/manual/metrics/index.md b/tutorial/content/labs/instrumentation/manual/metrics/index.md
index 1d668b5..e00804c 100644
--- a/tutorial/content/labs/instrumentation/manual/metrics/index.md
+++ b/tutorial/content/labs/instrumentation/manual/metrics/index.md
@@ -271,7 +271,7 @@ Each metric consists of two main parts.
 First, there is information to identify the instrument (e.g. name, kind, unit, and description).
 Second, the `data` second contains a list of `data_points`, which are measurements recorded by the instrument.
 Each measurement typically consists of a `value`, `attributes`, and a `timestamp`.
-The `aggregation_temporality` indicates whether the metric is cumulative, and is_monotonic specifies whether the metric only increases (or decreases, in the case of a gauge). This model is designed to be flexible and extensible, ensuring compatibility with existing monitoring systems and standards like Prometheus and StatsD, facilitating interoperability with various monitoring tools.
+The `aggregation_temporality` indicates whether the metric is cumulative, and `is_monotonic` specifies whether the metric only increases (or decreases, in the case of a gauge). This model is designed to be flexible and extensible, ensuring compatibility with existing monitoring systems and standards like Prometheus and StatsD, facilitating interoperability with various monitoring tools.
 
 ### metric dimensions