From 83bde57f6e549b017116d2c89ef427ea0fb8dad4 Mon Sep 17 00:00:00 2001
From: "Miss Islington (bot)"
 <31488909+miss-islington@users.noreply.github.com>
Date: Fri, 12 Aug 2022 21:05:37 -0700
Subject: [PATCH] Fix typo in internal/pycore_atomic.h (GH-95939)

(cherry picked from commit 8281cbddc6f0fbc94f0c21cacfac79a2d4057a4b)

Co-authored-by: fluesvamp <105884371+fluesvamp@users.noreply.github.com>
---
 Include/internal/pycore_atomic.h | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Include/internal/pycore_atomic.h b/Include/internal/pycore_atomic.h
index 3d42e54464c4..425d69f868b5 100644
--- a/Include/internal/pycore_atomic.h
+++ b/Include/internal/pycore_atomic.h
@@ -236,7 +236,7 @@ _Py_ANNOTATE_MEMORY_ORDER(const volatile void *address, _Py_memory_order order)
     in hardware they will fall back to a full memory barrier as well.
 
     This might affect performance but likely only in some very specific and
-    hard to meassure scenario.
+    hard to measure scenario.
 */
 #if defined(_M_IX86) || defined(_M_X64)
 typedef enum _Py_memory_order {
-- 
2.47.3