From 0fafb21057d7cfd5f380a0018a5d9e266974752e Mon Sep 17 00:00:00 2001
From: 01e9 <~@01eg.art>
Date: Thu, 19 Mar 2026 16:11:26 +0200
Subject: [PATCH] fixed broken links

re-apply https://github.com/boostorg/cobalt/pull/256
---
 doc/background/custom_executors.adoc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/background/custom_executors.adoc b/doc/background/custom_executors.adoc
index bb861b04..e4b410e1 100644
--- a/doc/background/custom_executors.adoc
+++ b/doc/background/custom_executors.adoc
@@ -1,11 +1,11 @@
 == Custom Executors
 
-One of the reasons cobalt defaults to https://www.boost.org/doc/libs/master/doc/html/boost_asio/reference/any_io_executor.html::[`asio::any_io_executor`]
+One of the reasons cobalt defaults to https://www.boost.org/doc/libs/master/doc/html/boost_asio/reference/any_io_executor.html[`asio::any_io_executor`]
 is that it is a type-erased executor, i.e. you can provide your own event-loop without needing to recompile `cobalt`.
 
 However, during the development of the Executor TS, the executor concepts got a bit unintuitive, to put it mildly.
 
-Ruben Perez wrote an excellent https://anarthal.github.io/cppblog/asio-props.html::[blog post], which I am shamelessly going to draw from.
+Ruben Perez wrote an excellent https://anarthal.github.io/cppblog/asio-props.html[blog post], which I am shamelessly going to draw from.
 
 === Definition