From 42478ff6fd15ac14fc5314e69556a4695a5b6013 Mon Sep 17 00:00:00 2001
From: Antoine Buchser <10513467+AntwaneB@users.noreply.github.com>
Date: Tue, 28 Oct 2025 09:35:05 +0000
Subject: [PATCH] Updated README to use the right case for the `set_property`
 function

The examples setting dimensions mentioned to use `setProperty` when dealing with high cardinality metrics. This should instead refer to `set_property`, which is the Python method and the one referred to throughout the rest of the README. The current casing might lead to confusion and make users believe there is a separate `setProperty` function.
---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 1903169..b5d2b6e 100644
--- a/README.md
+++ b/README.md
@@ -107,7 +107,7 @@ Adds a new set of dimensions that will be associated to all metric values.
 
 **WARNING**: Every distinct value will result in a new CloudWatch Metric.
 If the cardinality of a particular value is expected to be high, you should consider
-using `setProperty` instead.
+using `set_property` instead.
 
 Requirements:
 
@@ -128,7 +128,7 @@ Explicitly override all dimensions. By default, this will disable the default di
 
 **WARNING**: Every distinct value will result in a new CloudWatch Metric.
 If the cardinality of a particular value is expected to be high, you should consider
-using `setProperty` instead.
+using `set_property` instead.
 
 Requirements: