Update playing-with-buffers.md

Quatton · web-flow · commit b0b77fa17a94 · 2025-02-11T18:01:38.000+09:00
diff --git a/basic-3d-rendering/input-geometry/playing-with-buffers.md b/basic-3d-rendering/input-geometry/playing-with-buffers.md
@@ -353,7 +353,7 @@ while (!ready) {
 }
 ```
 
-You could now see `Buffer 2 mapped with status 1` (1 being the value of `BufferMapAsyncStatus::Success`) when running your program. **However**, we never change the `ready` variable to `true`! So the program then **halts forever**... not great. That is why the next section shows how to pass some context to the callback.
+You could now see `Buffer 2 mapped with status 1` (1 being the value of `BufferMapAsyncStatus::Success`) when running your program. **However**, we never change the `ready` variable to `true`! So the program then **hangs forever**... not great. That is why the next section shows how to pass some context to the callback.
 
 ### Mapping context
 

Original file line number	Diff line number	Diff line change
`@@ -353,7 +353,7 @@ while (!ready) {`
`353`	`353`	`}`
`354`	`354`	```
`355`	`355`
`356`		-You could now see `Buffer 2 mapped with status 1` (1 being the value of `BufferMapAsyncStatus::Success`) when running your program. However, we never change the `ready` variable to `true`! So the program then halts forever... not great. That is why the next section shows how to pass some context to the callback.
	`356`	+You could now see `Buffer 2 mapped with status 1` (1 being the value of `BufferMapAsyncStatus::Success`) when running your program. However, we never change the `ready` variable to `true`! So the program then hangs forever... not great. That is why the next section shows how to pass some context to the callback.
`357`	`357`
`358`	`358`	`### Mapping context`
`359`	`359`