Satisfying markdown lint.

Author: mwhittaker

rfcs/20260209-async-collectives.md

@@ -3,7 +3,7 @@
 Status: In Review<br/>
 Initial version: 02/09/2026<br/>
 Last updated: 02/23/2026<br/>
-Discussion thread: https://github.com/openxla/stablehlo/pull/2897/changes
+Discussion thread: [here][discussion_thread]
 
 ## Motivation
 
@@ -60,7 +60,7 @@ arguments. The op also has a single region that must contain only a call to one
 of the six collective ops. `async_start` returns a variadic number of futures.
 Here's an example:
 
-```
+```text
 "stablehlo.async_start"(%x) ({
   %y = "stablehlo.all_gather"(%x) {
     all_gather_dim = 1 : i64,
@@ -76,20 +76,20 @@ collective.
 We also introduce an `async_done` op which takes a variadic number of futures
 and unwraps them. Here's an example.
 
-```
+```text
 "stablehlo.async_done"(%f1, %f2) : (!stablehlo.future<tensor<4x4xf32>>, !stablehlo.future<tensor<2xf32>>) -> (tensor<4x4xf32>, tensor<2xf32>)
 ```
 
 ## Alternatives
 
 ### Fully Generic Async Ops
 
-https://github.com/openxla/stablehlo/pull/2551 is a StableHLO RFC that proposes
-adding generic `async_start` and `async_done` ops that can be used to call *any*
-function asynchronously, not just collectives. Here's an example from the RFC
-that performs an asynchronous add:
+[This][generic_async_rfc] is a StableHLO RFC that proposes adding generic
+`async_start` and `async_done` ops that can be used to call *any* function
+asynchronously, not just collectives. Here's an example from the RFC that
+performs an asynchronous add:
 
-```
+```text
 // %init_i: 2
 // %init_sum: 3
 %future = "stablehlo.async_start"(
@@ -123,7 +123,7 @@ These ops are identical to their non-asynchronous counterparts. They take the
 same arguments and have the same constraints. The only difference is that they
 return futures. Here's an example:
 
-```
+```text
 %future = "stablehlo.collective_permute_start"(%operand) {
   source_target_pairs = dense<[[0, 1], [1, 2]]> : tensor<2x2xi64>,
   channel_handle = #stablehlo.channel_handle<handle = 0, type = 0>
@@ -142,7 +142,7 @@ We could also introduce six **done ops**.
 A done op takes a `future<T>` as an argument and returns a `T`. Continuing the
 example above:
 
-```
+```text
 %result = "stablehlo.collective_permute_done"(%future) : (future<tensor<2x2xi64>>) -> tensor<2x2xi64>
 ```
 
@@ -152,7 +152,7 @@ Start ops could return regular tensors instead of futures. The value of these
 tensors, however, would be indeterminate. The tensors should not be used in any
 way besides as arguments to done ops. Here's an example:
 
-```
+```text
 %indeterminate = "stablehlo.collective_permute_start"(%operand) {
   source_target_pairs = dense<[[0, 1], [1, 2]]> : tensor<2x2xi64>,
   channel_handle = #stablehlo.channel_handle<handle = 0, type = 0>
@@ -168,7 +168,7 @@ introducing a new future type. However, it is less type-safe.
 This RFC has every collective return the same future type. Thus, the following
 code is well-typed but erroneous.
 
-```
+```text
 %future = "stablehlo.collective_permute_start"(%operand) {
   source_target_pairs = dense<[[0, 1], [1, 2]]> : tensor<2x2xi64>,
   channel_handle = #stablehlo.channel_handle<handle = 0, type = 0>
@@ -185,3 +185,5 @@ This would introduce more type safety.
 
 [async_collective_creator]: https://github.com/openxla/xla/blob/391c1c5fdadde89ee81886495d32dc32f9238af1/xla/hlo/transforms/collectives/async_collective_creator.h#L38
 [async_hlo]: https://openxla.org/xla/async_ops
+[discussion_thread]: https://github.com/openxla/stablehlo/pull/2897/changes
+[generic_async_rfc]: https://github.com/openxla/stablehlo/pull/2551