Fix Fiber#kill formatting

Author: zverok

3.3.md

@@ -8,9 +8,9 @@ description: Ruby 3.3 full and annotated changelog
 # Ruby 3.3
 
 * **Released at:** Dec 25, 2023 (<a class="github" href="https://github.com/ruby/ruby/blob/ruby_3_3/NEWS.md">NEWS.md</a> file)
-* **Status (as of Dec 27, 2023):** 3.3.0 is recently released
+* **Status (as of Dec 28, 2023):** 3.3.0 is recently released
 * **This document first published:** Dec 25, 2023
-* **Last change to this document:** Dec 27, 2023
+* **Last change to this document:** Dec 28, 2023
 
 <!--
 * **Reason:**
@@ -430,7 +430,7 @@ A new "weak map" concept implementation. Unlike `ObjectSpace::WeakMap`, it compa
 * **Documentation:** <a class="ruby-doc" href="https://docs.ruby-lang.org/en/master/ObjectSpace/WeakKeyMap.html"><code>ObjectSpace::WeakKeyMap</code></a>
 * **Code:**
   ```ruby
-  map = ObjectSpace::WeekMap.new
+  map = ObjectSpace::WeakKeyMap.new
 
   key = "foo"
   map[key] = true
@@ -739,20 +739,20 @@ Terminates the Fiber by sending an exception inside it.
 * **Notes:**
   * The exception sent to Fiber is _uncatchable_ (so no `rescue Exception` will notice it), so it can't be said that it has some _class_; the only usage of the fact that it is raised through exception mechanism is invoking `ensure` block;
   * The fibers that was invoking the killed one with `resume` or `transfer`, receives `nil` from that call;
-  ```ruby
-  f1 = Fiber.new {
-    # Instead of yielding something back, the fiber kills itself
-    Fiber.current.kill
-  }
-
-  f2 = Fiber.new {
-    result = f1.transfer
-    p(result:)
-  }
-
-  f2.resume
-  # prints: {:result => nil}
-  ```
+    ```ruby
+    f1 = Fiber.new {
+      # Instead of yielding something back, the fiber kills itself
+      Fiber.current.kill
+    }
+
+    f2 = Fiber.new {
+      result = f1.transfer
+      p(result:)
+    }
+
+    f2.resume
+    # prints: {:result => nil}
+    ```
   * Only fibers belonging to the same thread can be killed.
 
 ### Internals[](#internals)

_src/3.3.md

@@ -739,20 +739,20 @@ Terminates the Fiber by sending an exception inside it.
 * **Notes:**
   * The exception sent to Fiber is _uncatchable_ (so no `rescue Exception` will notice it), so it can't be said that it has some _class_; the only usage of the fact that it is raised through exception mechanism is invoking `ensure` block;
   * The fibers that was invoking the killed one with `resume` or `transfer`, receives `nil` from that call;
-  ```ruby
-  f1 = Fiber.new {
-    # Instead of yielding something back, the fiber kills itself
-    Fiber.current.kill
-  }
-
-  f2 = Fiber.new {
-    result = f1.transfer
-    p(result:)
-  }
-
-  f2.resume
-  # prints: {:result => nil}
-  ```
+    ```ruby
+    f1 = Fiber.new {
+      # Instead of yielding something back, the fiber kills itself
+      Fiber.current.kill
+    }
+
+    f2 = Fiber.new {
+      result = f1.transfer
+      p(result:)
+    }
+
+    f2.resume
+    # prints: {:result => nil}
+    ```
   * Only fibers belonging to the same thread can be killed.
 
 ### Internals