Update proposals/NNNN-global-actor-isolated-types-usability.md

Co-authored-by: John McCall <[email protected]>

Author: simanerush

proposals/NNNN-global-actor-isolated-types-usability.md

@@ -101,7 +101,8 @@ We propose that:
 
 - Stored properties of `Sendable` type in a global-actor-isolated value type can be declared as `nonisolated` without using `(unsafe)`.
 - Stored properties of `Sendable` type in a global-actor-isolated value type are treated as `nonisolated` when used within the module or if the value type is `frozen`.
-- `@Sendable` would be inferred for global-actor-isolated functions and closures. Additionally, globally isolated closures would be allowed to capture non-`Sendable` values.
+- `@Sendable` is inferred for global-actor-isolated functions and closures.
+- Global-actor-isolated closures are allowed to capture non-`Sendable` values despite being `@Sendable`.
 - The programmer would be able to suppress the automatic conformance inferred via the above rule using the new `@~Sendable` attribute. By analogy, introduce a new `~Sendable` protocol to indicate that a nominal type is not `Sendable`.
 - Require the global-actor-isolated subclass of a `nonisolated`, non-`Sendable` to be non-`Sendable`.