From 545d30a33abe5a592b9ee020b320d5742e0b6784 Mon Sep 17 00:00:00 2001
From: DJGosnell <DJGosnell@gmail.com>
Date: Mon, 16 Oct 2023 13:53:56 -0400
Subject: [PATCH] Fix for table.

---
 README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index e4fe7a7..41858c0 100644
--- a/README.md
+++ b/README.md
@@ -101,12 +101,12 @@ MaxWarmupIterationCount=3  MinIterationCount=3  MinWarmupIterationCount=1
 ## Method Invocation Table
 Some methods are handled differently based upon the arguments passed and there are limitations placed upon the types of arguments which can be used together.  Most of these incompatibilities handled with Diagnostic Errors provided by the `NexNet.Generator`.  Below is a table which shows valid combinations of arguments and return values.
 
-|              | CancellationToken | INexusDuplexPipe | INexusChannel<T> | Args |
-|--------------|-------------------|------------------|------------------|------|
-| void         |                   |                  |                  | X    |
-| ValueTask    | X                 |                  |                  | X    |
-| ValueTask    |                   | X                | X                | X    |
-| ValueTask<T> | X                 |                  |                  | X    |
+|                    | CancellationToken | INexusDuplexPipe | INexusChannel<T> | Args |
+|--------------------|-------------------|------------------|------------------|------|
+| void               |                   |                  |                  | X    |
+| ValueTask          | X                 |                  |                  | X    |
+| ValueTask          |                   | X                | X                | X    |
+| ValueTask&lt;T&gt; | X                 |                  |                  | X    |
 
 Notes:
 - `CancellationToken`s can't be combined with `NexusDuplexPipe` nor `INexusChannel<T>` due to pipes/channels having built-in cancellation/completion notifications.