Fix formatting of release notes.

Author: ioquatix

releases.md

@@ -78,7 +78,7 @@ queue.dequeue          # => nil
 
 ## v2.25.0
 
-	- Added support for `io_select` hook in the fiber scheduler, allowing non-blocking `IO.select` operations. This enables better integration with code that uses `IO.select` for multiplexing IO operations.
+  - Added support for `io_select` hook in the fiber scheduler, allowing non-blocking `IO.select` operations. This enables better integration with code that uses `IO.select` for multiplexing IO operations.
 
 ### Use `IO::Event::WorkerPool` for Blocking Operations
 
@@ -105,9 +105,8 @@ end
 
 ## v2.24.0
 
-	- Ruby v3.1 support is dropped.
-	- `Async::Wrapper` which was previously deprecated, is now removed.
-	- `Async::Barrier` now waits in order of completion rather than order of creation. This means that if you create a barrier with 3 tasks, and one of them completes (or fails) before the others, it will be the first to be yielded to the barrier.
+  - Ruby v3.1 support is dropped.
+  - `Async::Wrapper` which was previously deprecated, is now removed.
 
 ### Flexible Timeouts
 
@@ -139,7 +138,7 @@ end
 
 ## v2.23.0
 
-	- Rename `ASYNC_SCHEDULER_DEFAULT_WORKER_POOL` to `ASYNC_SCHEDULER_WORKER_POOL`.
+  - Rename `ASYNC_SCHEDULER_DEFAULT_WORKER_POOL` to `ASYNC_SCHEDULER_WORKER_POOL`.
 
 ### Fiber Stall Profiler
 
@@ -169,7 +168,7 @@ Ruby 3.4 will feature a new fiber scheduler hook, `blocking_operation_wait` whic
 
 The Async scheduler optionally supports this feature using a worker pool, by using the following environment variable:
 
-		ASYNC_SCHEDULER_WORKER_POOL=true
+    ASYNC_SCHEDULER_WORKER_POOL=true
 
 This will cause the scheduler to use a worker pool for general blocking operations, rather than blocking the event loop.
 
@@ -189,21 +188,21 @@ To take advantage of this feature, you will need to introduce your own `config/t
 
 Occasionally on issues, I encounter people asking for help and I need more information. Pressing Ctrl-C to exit a hung program is common, but it usually doesn't provide enough information to diagnose the problem. Setting the `CONSOLE_LEVEL=debug` environment variable will now print additional information about the scheduler when you interrupt it, including a backtrace of the current tasks.
 
-		> CONSOLE_LEVEL=debug bundle exec ruby ./test.rb
-		^C  0.0s    debug: Async::Reactor [oid=0x974] [ec=0x988] [pid=9116] [2024-11-08 14:12:03 +1300]
-									 | Scheduler interrupted: Interrupt
-									 | #<Async::Reactor:0x0000000000000974 1 children (running)>
-									 | 	#<Async::Task:0x000000000000099c /Users/samuel/Developer/socketry/async/lib/async/scheduler.rb:185:in `transfer' (running)>
-									 | 	→ /Users/samuel/Developer/socketry/async/lib/async/scheduler.rb:185:in `transfer'
-									 | 	  /Users/samuel/Developer/socketry/async/lib/async/scheduler.rb:185:in `block'
-									 | 	  /Users/samuel/Developer/socketry/async/lib/async/scheduler.rb:207:in `kernel_sleep'
-									 | 	  /Users/samuel/Developer/socketry/async/test.rb:7:in `sleep'
-									 | 	  /Users/samuel/Developer/socketry/async/test.rb:7:in `sleepy'
-									 | 	  /Users/samuel/Developer/socketry/async/test.rb:12:in `block in <top (required)>'
-									 | 	  /Users/samuel/Developer/socketry/async/lib/async/task.rb:197:in `block in run'
-									 | 	  /Users/samuel/Developer/socketry/async/lib/async/task.rb:420:in `block in schedule'
-		/Users/samuel/Developer/socketry/async/lib/async/scheduler.rb:317:in `select': Interrupt
-		... (backtrace continues) ...
+    > CONSOLE_LEVEL=debug bundle exec ruby ./test.rb
+    ^C  0.0s    debug: Async::Reactor [oid=0x974] [ec=0x988] [pid=9116] [2024-11-08 14:12:03 +1300]
+                   | Scheduler interrupted: Interrupt
+                   | #<Async::Reactor:0x0000000000000974 1 children (running)>
+                   | 	#<Async::Task:0x000000000000099c /Users/samuel/Developer/socketry/async/lib/async/scheduler.rb:185:in `transfer' (running)>
+                   | 	→ /Users/samuel/Developer/socketry/async/lib/async/scheduler.rb:185:in `transfer'
+                   | 	  /Users/samuel/Developer/socketry/async/lib/async/scheduler.rb:185:in `block'
+                   | 	  /Users/samuel/Developer/socketry/async/lib/async/scheduler.rb:207:in `kernel_sleep'
+                   | 	  /Users/samuel/Developer/socketry/async/test.rb:7:in `sleep'
+                   | 	  /Users/samuel/Developer/socketry/async/test.rb:7:in `sleepy'
+                   | 	  /Users/samuel/Developer/socketry/async/test.rb:12:in `block in <top (required)>'
+                   | 	  /Users/samuel/Developer/socketry/async/lib/async/task.rb:197:in `block in run'
+                   | 	  /Users/samuel/Developer/socketry/async/lib/async/task.rb:420:in `block in schedule'
+    /Users/samuel/Developer/socketry/async/lib/async/scheduler.rb:317:in `select': Interrupt
+    ... (backtrace continues) ...
 
 This gives better visibility into what the scheduler is doing, and should help diagnose issues.
 
@@ -220,19 +219,19 @@ Async{raise "Boom"}
 
 Will now use `Kernel#warn` to print the task failure warning:
 
-		#<Async::Task:0x00000000000012d4 /home/samuel/Developer/socketry/async/lib/async/task.rb:104:in `backtrace' (running)>
-		Task may have ended with unhandled exception.
-		(irb):4:in `block in <top (required)>': Boom (RuntimeError)
-			from /home/samuel/Developer/socketry/async/lib/async/task.rb:197:in `block in run'
-			from /home/samuel/Developer/socketry/async/lib/async/task.rb:420:in `block in schedule'
+    #<Async::Task:0x00000000000012d4 /home/samuel/Developer/socketry/async/lib/async/task.rb:104:in `backtrace' (running)>
+    Task may have ended with unhandled exception.
+    (irb):4:in `block in <top (required)>': Boom (RuntimeError)
+    	from /home/samuel/Developer/socketry/async/lib/async/task.rb:197:in `block in run'
+    	from /home/samuel/Developer/socketry/async/lib/async/task.rb:420:in `block in schedule'
 
 ## v2.18.0
 
-	- Add support for `Sync(annotation:)`, so that you can annotate the block with a description of what it does, even if it doesn't create a new task.
+  - Add support for `Sync(annotation:)`, so that you can annotate the block with a description of what it does, even if it doesn't create a new task.
 
 ## v2.17.0
 
-	- Introduce `Async::Queue#push` and `Async::Queue#pop` for compatibility with `::Queue`.
+  - Introduce `Async::Queue#push` and `Async::Queue#pop` for compatibility with `::Queue`.
 
 ## v2.16.0
 
@@ -249,7 +248,7 @@ reactor = Async::Reactor.new # internally calls Fiber.set_scheduler
 
 # This should run in the above reactor, rather than creating a new one.
 Async do
-	puts "Hello World"
+  puts "Hello World"
 end
 ```