Fix docs

Author: gjcairo

Sources/GRPCCore/Documentation.docc/Development/Design.md

@@ -173,12 +173,12 @@ concurrency.
 Most users won't use ``GRPCClient`` to execute RPCs directly, instead they will
 use the generated client stubs which wrap the ``GRPCClient``. Users are
 responsible for creating the client and running it (which starts and runs the
-underlying transport). This is done by calling ``GRPCClient/run()``. The client
+underlying transport). This is done by calling ``GRPCClient/runConnections()``. The client
 can be shutdown gracefully by calling ``GRPCClient/beginGracefulShutdown()``
 which will stop new RPCs from starting (by failing them with
 ``RPCError/Code-swift.struct/unavailable``) but allow existing ones to continue.
 Existing work can be stopped more abruptly by cancelling the task where
-``GRPCClient/run()`` is executing.
+``GRPCClient/runConnections()`` is executing.
 
 #### Server
 

Sources/GRPCCore/GRPCClient.swift

@@ -231,7 +231,7 @@ public final class GRPCClient<Transport: ClientTransport>: Sendable {
   ///
   /// The transport will be closed: this means that it will be given enough time to wait for
   /// in-flight RPCs to finish executing, but no new RPCs will be accepted. You can cancel the task
-  /// executing ``run()`` if you want to abruptly stop in-flight RPCs.
+  /// executing ``runConnections()`` if you want to abruptly stop in-flight RPCs.
   public func beginGracefulShutdown() {
     let wasRunning = self.stateMachine.withLock { $0.state.beginGracefulShutdown() }
     if wasRunning {