run -> thenRun

packages/docs/docs/forms.md

@@ -82,7 +82,7 @@ const CreateProfileView = Component.make("CreateProfile")(function* () {
         Effect.log(
           `Creating ${profile.displayName}, age ${profile.age}`,
         ),
-    }).pipe(MutationForm.run),
+    }).pipe(MutationForm.thenRun),
   )
 
   const [canCommit, isCommitting] = yield* View.useAll([
@@ -108,7 +108,7 @@ mutation receives the schema's decoded profile, so `profile.age` is a number.
 Schema transformations happen before the mutation and schema issues prevent an
 invalid draft from being submitted.
 
-`MutationForm.run` starts initial validation. In the example above,
+`MutationForm.thenRun` starts initial validation. In the example above,
 `Component.useOnMount` keeps that validation and the form's mutation work tied
 to the component that owns them.
 
@@ -137,7 +137,7 @@ const EditProfileView = Component.make("EditProfile")(function* () {
       const form = yield* LensForm.make({
         schema: ProfileSchema,
         target: profile,
-      }).pipe(LensForm.run)
+      }).pipe(LensForm.thenRun)
 
       return [form, profile] as const
     }),
@@ -432,7 +432,7 @@ const AppointmentView = Component.make("Appointment")(function* () {
           Effect.log(
             `Saving ${DateTime.formatIso(appointment.startsAt)}`,
           ),
-      }).pipe(MutationForm.run)
+      }).pipe(MutationForm.thenRun)
 
       return [form, Form.focusObjectOn(form, "startsAt")] as const
     }),

packages/docs/docs/query.md

@@ -60,7 +60,7 @@ A query is driven by a `View` rather than by a value read during one React
 render. Whenever that key changes, a running Query checks the cache and starts
 the query effect when necessary.
 
-`Query.make` constructs the Query and `Query.run` starts it in the current
+`Query.make` constructs the Query and `Query.thenRun` starts it in the current
 scope. Create each query instance once and keep it stable. In a component, the usual place is
 `Component.useOnMount`; a query shared by multiple components can instead be
 owned by an Effect service. Change the existing query's reactive key rather
@@ -95,7 +95,7 @@ const PostView = Component.make("Post")(function* () {
             Effect.andThen((response) => response.json),
             Effect.andThen(Schema.decodeUnknownEffect(Post)),
           ),
-      }).pipe(Query.run)
+      }).pipe(Query.thenRun)
 
       return [Lens.focusTupleAt(key, 1), query] as const
     }),
@@ -124,7 +124,7 @@ Effect equality by default, so structurally equal Effect data types work well
 as query keys. Supply `keyEquivalence` when the key needs different equality
 semantics.
 
-`Query.run` starts watching its key in the current scope. The
+`Query.thenRun` starts watching its key in the current scope. The
 `Component.useOnMount` call above keeps both the query instance and its query
 function identity stable for the component's lifetime.
 
@@ -256,7 +256,7 @@ Refresh every five minutes, starting after five minutes:
 import { Schedule } from "effect"
 
 const query = yield* Query.make(options).pipe(
-  Query.run,
+  Query.thenRun,
   Query.withScheduledRefresh(Schedule.spaced("5 minutes")),
 )
 ```
@@ -265,7 +265,7 @@ Limit the number of refreshes:
 
 ```ts
 const query = yield* Query.make(options).pipe(
-  Query.run,
+  Query.thenRun,
   Query.withScheduledRefresh(
     Schedule.spaced("5 minutes").pipe(
       Schedule.upTo({ times: 3 }),
@@ -296,7 +296,7 @@ const query = yield* Query.make({
   f: loadPost,
   staleTime: "10 seconds",
   refreshOnWindowFocus: false,
-}).pipe(Query.run)
+}).pipe(Query.thenRun)
 ```
 
 Window-focus refresh depends on the optional `@effect/platform-browser`