From ed8ff48e25d171a19f17f6799c8e51972bdf732c Mon Sep 17 00:00:00 2001
From: nomicon-kr <djwodus18@naver.com>
Date: Thu, 26 Sep 2024 16:47:04 +0900
Subject: [PATCH] Update checked-uninit.md

---
 src/checked-uninit.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/checked-uninit.md b/src/checked-uninit.md
index 37cbea2..9b01f06 100644
--- a/src/checked-uninit.md
+++ b/src/checked-uninit.md
@@ -1,8 +1,6 @@
-# Checked Uninitialized Memory
+# 검사받는 초기화되지 않은 메모리
 
-Like C, all stack variables in Rust are uninitialized until a value is
-explicitly assigned to them. Unlike C, Rust statically prevents you from ever
-reading them until you do:
+C와 같이, 러스트에서 모든 스택 변수는 값이 배정되기 전까지 초기화되지 않은 상태입니다. C와 다르게, 러스트는 값을 배정하기 전에 그 변수들을 읽는 것을 컴파일 때 방지합니다:
 
 ```rust,compile_fail
 fn main() {
@@ -17,6 +15,8 @@ fn main() {
   |                    ^ use of possibly uninitialized `x`
 ```
 
+
+
 This is based off of a basic branch analysis: every branch must assign a value
 to `x` before it is first used. For short, we also say that "`x` is init" or
 "`x` is uninit".