Fix typo

Author: akarnokd

DESIGN.md

@@ -364,7 +364,7 @@ Therefore, new standard factory methods will try to address the common entry poi
   - `create(AsyncGenerator<T, S>)` to batch-create signals based on request patterns
   - `create(Consumer<? super SingleEmitter<T>>)` to relay a single value or error from other reactive sources (i.e., addListener callbacks)
   - `create(Consumer<? super FlowEmitter<T>>)` to relay multiple values or error from multi-valued reactive-sources (i.e., button-clicks) while also give flow control options right there (buffer, drop, error, etc.).
-  - `create(Consumer<? super CompletionEmitter>)` signal a completion or error from valueless reactive sources
+  - `create(Consumer<? super CompletionEmitter)>` signal a completion or error from valueless reactive sources
 
 The following table lists where these create methods will be available in respect of the base types:
 
@@ -374,7 +374,7 @@ The following table lists where these create methods will be available in respec
 | `create(AsyncOnSubscribe<T, S>)` | Yes | No | No | No |
 | `create(Consumer<? super SingleEmitter<T>>)` | Yes | Yes | Yes | No |
 | `create(Consumer<? super FlowEmitter<T>>)` | Yes | Yes | Yes | No |
-| `create(Consumer<? super CompletionEmitter)>` | Yes | Yes | No | Yes |
+| `create(Consumer<? super CompletionEmitter>)` | Yes | Yes | No | Yes |
 
 The first two `create` methods take an implementation of an interface which provides state and the generator methods: