Incorporate tech review

Co-authored-by: Doug Gregor <[email protected]>

Author: amartini51

TSPL.docc/ReferenceManual/Attributes.md

@@ -1314,19 +1314,20 @@ this attribute reduces the strictness of concurrency checking
 for code that uses types from the imported module.
 Specifically,
 types from the imported module
-that aren't explicitly marked as either sendable or nonsendable
+that aren't explicitly marked as nonsendable
 can be used in a context that requires sendable types.
 
 On other declarations,
 this attribute reduces the strictness of concurrency checking
 for code that uses the symbol being declared.
 When you use this symbol in a scope that has minimal concurrency checking,
-you can use members of this type
-that aren't explicitly marked as either sendable or nonsendable
-in a context that requires sendable types.
+concurrency-related constraints specified by that symbol,
+such as `Sendable` requirements or global actors,
+aren't checked.
 You can apply this attribute
 to the following kinds of declarations:
 
+- Imports
 - Structures, classes, and actors
 - Enumerations and enumeration cases
 - Protocols
@@ -1339,15 +1340,21 @@ You can use this attribute as follows,
 to aid in migrating code to strict concurrency checking:
 
 1. Enable strict checking.
-1. Annotate imports and declarations that need to be migrated
-   with the `preconcurrency` attribute.
-1. After migrating a declaration,
-   remove the `preconcurrency` attribute from it.
-1. After migrating a module,
-   the compiler will warn you about
+1. Annotate imports with the `preconcurrency` attribute
+   for modules that haven't enabled strict checking.
+1. After migrating a module to strict checking,
+   remove the `preconcurrency` attribute.
+   The compiler warns you about
    any places where the `preconcurrency` attribute on an import
    no longer has an effect and should be removed.
 
+For other declarations,
+add the `preconcurrency` attribute
+when you add concurrency-related constraints to the declaration,
+if you still have clients
+that haven't migrated to strict checking.
+Remove the `preconcurrency` attribute after all your clients have migrated.
+
 Declarations from Objective-C are always imported
 as if they were marked with the `preconcurrency` attribute.