@@ -41,7 +41,7 @@ pub trait SetTarget<C> {
41
41
///
42
42
/// This is mostly to get around that `Clone` requires `Sized` and so you need this
43
43
/// trick to get a copy of the `Box<dyn SetTarget<C>>` you got from making the
44
- /// reconneting client.
44
+ /// reconnecting client.
45
45
fn add_ref ( & self ) -> Box < dyn SetTarget < C > > ;
46
46
47
47
/// Sets the target client of the reconnecting client that this trait implementation is
@@ -258,16 +258,16 @@ where
258
258
259
259
/// Creates a new client that reconnects when getting [`ErrorKind::Disconnected`](capnp::ErrorKind::Disconnected) errors.
260
260
///
261
- /// Usually when you get a [`Disconnected`](capnp::ErrorKind::Disconnected) error respoonse from calling a method on a capability
261
+ /// Usually when you get a [`Disconnected`](capnp::ErrorKind::Disconnected) error response from calling a method on a capability
262
262
/// it means the end of that capability for good. And so you can't call methods on that
263
263
/// capability any more.
264
264
///
265
265
/// When you have a way of getting the capability back: Be it from a bootstrap or because
266
- /// the capability is persistent this method can help you wrap that reconnnection logic into a client
266
+ /// the capability is persistent this method can help you wrap that reconnection logic into a client
267
267
/// that automatically runs the logic whenever a method call returns [`Disconnected`](capnp::ErrorKind::Disconnected).
268
268
///
269
269
/// The way it works is that you provide a closure that returns a fresh client or a permanent error and
270
- /// you get a new conected client and a [`SetTarget`] interface that you can optionally use to prematurely
270
+ /// you get a new connected client and a [`SetTarget`] interface that you can optionally use to prematurely
271
271
/// replace the client.
272
272
///
273
273
/// There is one caveat though: The original request that got a [`Disconnected`](capnp::ErrorKind::Disconnected)
@@ -334,7 +334,7 @@ where
334
334
/// For explanation of how this functions see: [`auto_reconnect`]
335
335
///
336
336
/// The main difference between [`auto_reconnect`] and this function is that while [`auto_reconnect`] will call
337
- /// the closure immediatly to get an inner client to wrap, this function starts out disconnected and only calls
337
+ /// the closure immediately to get an inner client to wrap, this function starts out disconnected and only calls
338
338
/// the closure to get the actual client when the capability is first used.
339
339
pub fn lazy_auto_reconnect < F , C > ( connect : F ) -> ( C , Box < dyn SetTarget < C > > )
340
340
where
0 commit comments