fixed some formatting issues

Author: dietmarkuehl

docs/issues-overview.md

@@ -96,7 +96,7 @@ the respective issue):
 
 - the wording is unclear
 - fix: two versions
-- comment: I think I had the 2nd in mind 
+- comment: I think I had the 2nd in mind
 
 => allow affine_on to complete inline regardless that's the difference to continues_on
    in addition it can be customized separately
@@ -117,7 +117,7 @@ the respective issue):
 - non-success completions don't guarantee affinity invariant
 - fix: suppress stop token
 - comment: in case of `set_stopped()` the coroutine doesn't resume; for `set_error(e)` other reasons may exist
-- comment: however, I don't object to this direction 
+- comment: however, I don't object to this direction
 
 => this requirement needs to align with what continues_on does
 - the actual conclusion is: affine_on may need to do what continues_on does

examples/issue-frame-allocator.cpp

@@ -13,10 +13,10 @@ template <typename Env>
 ex::task<int, Env> test(int i, auto&&...) {
     co_return co_await ex::just(i);
 }
-    struct default_env {};
-    struct allocator_env {
-        using allocator_type = std::pmr::polymorphic_allocator<>;
-    };
+struct default_env {};
+struct allocator_env {
+    using allocator_type = std::pmr::polymorphic_allocator<>;
+};
 
 int main() {
     ex::sync_wait(test<default_env>(17));                                            // OK: no allocator

examples/issue-symmetric-transfer.cpp

@@ -20,7 +20,7 @@ int main() {
     struct inline_env {
         using scheduler_type = ex::inline_scheduler;
     };
-    [[maybe_unused]] inline_env ev{};
+    [[maybe_unused]] inline_env                 ev{};
     [[maybe_unused]] inline_env::scheduler_type sched{};
     ex::sync_wait(test<affine_env>()); // OK
     // ex::sync_wait(test<inline_env>()); // error: stack overflow