From f5d4984274809b024ce9c127f844105744b5e3ee Mon Sep 17 00:00:00 2001
From: Sergey Bogolepov <1580082+sbogolepov@users.noreply.github.com>
Date: Thu, 26 Jan 2023 17:49:06 +0200
Subject: [PATCH] Update HACKING.md

---
 kotlin-native/HACKING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kotlin-native/HACKING.md b/kotlin-native/HACKING.md
index 029dc5c724b..401335548f2 100644
--- a/kotlin-native/HACKING.md
+++ b/kotlin-native/HACKING.md
@@ -386,7 +386,7 @@ It is possible to dump LLVM IR after a particular compiler phase.
 kotlinc-native main.kt -Xsave-llvm-ir-after=<PhaseName> -Xsave-llvm-ir-directory=<PATH>
 ```
 
-`<PATH>/out.<PhaseName>.ll` will contain LLVM IR after LLVM optimization pipeline.
+`<PATH>/out.<PhaseName>.ll` will contain LLVM IR after given phase.
 
 Passing `Codegen` phase allows to get LLVM IR right after translation from Kotlin Backend IR, and
 `BitcodeOptimization` phase allows to see the result of LLVM optimization pipeline. The list of phases that support LLVM IR dumping is constantly changing, so check out compiler sources