From e0df461d6949780a349b5efb3d8248e64638f6a7 Mon Sep 17 00:00:00 2001 From: Tiago Farias Date: Sun, 28 Aug 2022 15:40:50 +0200 Subject: [PATCH] Update capsule.md (#5497) --- docs/capsule.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/capsule.md b/docs/capsule.md index 55341326..b2e14b9a 100644 --- a/docs/capsule.md +++ b/docs/capsule.md @@ -47,7 +47,7 @@ Sidekiq.configure_server do |config| end ``` -Capsules can have their own customzied middleware chains but by default will inherit the global middleware configuration. Each Capsule will have its own Redis connection pool sized to the configured concurrency. +Capsules can have their own customized middleware chains but by default will inherit the global middleware configuration. Each Capsule will have its own Redis connection pool sized to the configured concurrency. `Sidekiq::Launcher` is the top-level component which takes a `Sidekiq::Config` and launches the tree of runtime components for each capsule. Once passed to Launcher, the global Config and each Capsule should be considered frozen and immutable. @@ -136,5 +136,5 @@ Sidekiq::Capsule overrides Sidekiq::Config in order to provide Capsule-local res you'll see places within Sidekiq where Capsule acts like a Config. With this pattern, we greatly reduce the use of global APIs throughout Sidekiq internals. -Where beforefore we'd call `Sidekiq.xyz`, we instead provide similar functionality like -`config.xyz`. \ No newline at end of file +Where before we'd call `Sidekiq.xyz`, we instead provide similar functionality like +`config.xyz`.