From 012a9de7fbcd36376a9f4cfa00954ae032c92489 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?=D0=95=D0=B2=D0=B3=D0=B5=D0=BD=D0=B8=D0=B9=20=D0=9C=D0=B8?=
 =?UTF-8?q?=D1=85=D0=B0=D0=B9=D0=BB=D0=BE=D0=B2=D0=B8=D1=87=20=D0=96=D0=B5?=
 =?UTF-8?q?=D0=BB=D0=B5=D0=BD=D1=81=D0=BA=D0=B8=D0=B9?=
 <55230817+zhelenskiy@users.noreply.github.com>
Date: Wed, 3 May 2023 22:23:02 +0200
Subject: [PATCH] Fix statics.md

Fix a typo
---
 proposals/statics.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/proposals/statics.md b/proposals/statics.md
index 6134acd16..df199a7bf 100644
--- a/proposals/statics.md
+++ b/proposals/statics.md
@@ -1967,7 +1967,7 @@ performance is a secondary concern, if a concern at all. For performance-sensiti
 opt-in capabilities to be used by experts who write performance-sensitive code. One such performance-oriented
 capability is a `value class`, and another such performance-oriented capability is a `static object`.
 They take away performance-affecting "provides a stable reference" feature of classes and objects respectively
-for those cases where you can do away without it. If you take legal Kotlin code and replace `value class` with `class`
+for those cases where you can do away without it. If you take legal Kotlin code and replace `value class` with `data class`
 and `static object` with `object` the code will mostly compile and work as before
 (maybe with few non-essential differences), but will lose some efficiency.