diff --git a/lib/nebulex/adapters/local.ex b/lib/nebulex/adapters/local.ex
index 7a21931f..6995727b 100644
--- a/lib/nebulex/adapters/local.ex
+++ b/lib/nebulex/adapters/local.ex
@@ -175,7 +175,7 @@ defmodule Nebulex.Adapters.Local do
   mechanism is pushing a new cache generation and remove the oldest one. In
   this way, we ensure only the most frequently used keys are always available
   in the newer generation and the the least frequently used are evicted when
-  the garbage collector runs, and the garbage collector is triggered uppon
+  the garbage collector runs, and the garbage collector is triggered upon
   these conditions:
 
     * When the time interval defined by `:gc_interval` is completed.
diff --git a/lib/nebulex/adapters/local/generation.ex b/lib/nebulex/adapters/local/generation.ex
index 62136fb5..ccfb4312 100644
--- a/lib/nebulex/adapters/local/generation.ex
+++ b/lib/nebulex/adapters/local/generation.ex
@@ -6,7 +6,7 @@ defmodule Nebulex.Adapters.Local.Generation do
   known as generations, based on age of the objects. An object is allocated
   in the youngest generation, sometimes called the nursery, and is promoted
   to an older generation if its lifetime exceeds the threshold of its current
-  generation (defined by option `:gc_interval`). Everytime the GC runs
+  generation (defined by option `:gc_interval`). Every time the GC runs
   (triggered by `:gc_interval` timeout), a new cache generation is created
   and the oldest one is deleted.
 
@@ -84,7 +84,7 @@ defmodule Nebulex.Adapters.Local.Generation do
   ## API
 
   @doc """
-  Starts the garbage collector for the build-in local cache adapter.
+  Starts the garbage collector for the built-in local cache adapter.
   """
   @spec start_link(opts) :: GenServer.on_start()
   def start_link(opts) do
diff --git a/lib/nebulex/adapters/partitioned.ex b/lib/nebulex/adapters/partitioned.ex
index d7bfdc54..173acde7 100644
--- a/lib/nebulex/adapters/partitioned.ex
+++ b/lib/nebulex/adapters/partitioned.ex
@@ -48,7 +48,7 @@ defmodule Nebulex.Adapters.Partitioned do
       However, this adapter does not provide fault-tolerance implementation,
       each piece of data is kept in a single node/machine (via sharding), then,
       if a node fails, the data kept by this node won't be available for the
-      rest of the cluster memebers.
+      rest of the cluster members.
 
   > Based on **"Distributed Caching Essential Lessons"** by **Cameron Purdy**
     and [Coherence Partitioned Cache Service][oracle-pcs].
diff --git a/lib/nebulex/adapters/replicated.ex b/lib/nebulex/adapters/replicated.ex
index 377a0681..a0518ae9 100644
--- a/lib/nebulex/adapters/replicated.ex
+++ b/lib/nebulex/adapters/replicated.ex
@@ -189,7 +189,7 @@ defmodule Nebulex.Adapters.Replicated do
         ```
 
     * `telemetry_prefix ++ [:bootstrap]` - Dispatched by the adapter at start
-      time when there are errors while synching up with the cluster nodes.
+      time when there are errors while syncing up with the cluster nodes.
 
       * Measurements:
 
@@ -220,7 +220,7 @@ defmodule Nebulex.Adapters.Replicated do
   or alter the cache somehow to ensure as much consistency as possible across
   all members of the cluster. These locks may be per key or for the entire cache
   depending on the operation taking place. For that reason, it is very important
-  to be aware about those operation that can potentally lead to performance and
+  to be aware about those operation that can potentially lead to performance and
   scalability issues, so that you can do a better usage of the replicated
   adapter. The following is with the operations and aspects you should pay
   attention to:
diff --git a/lib/nebulex/cache.ex b/lib/nebulex/cache.ex
index f5f2950e..30b8636e 100644
--- a/lib/nebulex/cache.ex
+++ b/lib/nebulex/cache.ex
@@ -176,7 +176,7 @@ defmodule Nebulex.Cache do
 
   **NOTE:** The events outlined above are the recommended for the adapters
   to dispatch. However, it is highly recommended to review the used adapter
-  documentation to ensure it is fullly compatible with these events, perhaps
+  documentation to ensure it is fully compatible with these events, perhaps
   differences, or perhaps also additional events.
 
   ## Stats
@@ -1302,7 +1302,7 @@ defmodule Nebulex.Cache do
     * `:return` - Tells the query what to return from the matched entries.
       See the possible values in the "Query return option" section below.
       The default depends on the adapter, for example, the default for the
-      built-in adapters is `:key`. This option is supported by the build-in
+      built-in adapters is `:key`. This option is supported by the built-in
       adapters, but it is recommended to see the adapter's documentation
       to confirm its compatibility with this option.
 
@@ -1407,7 +1407,7 @@ defmodule Nebulex.Cache do
     * `:return` - Tells the query what to return from the matched entries.
       See the possible values in the "Query return option" section below.
       The default depends on the adapter, for example, the default for the
-      built-in adapters is `:key`. This option is supported by the build-in
+      built-in adapters is `:key`. This option is supported by the built-in
       adapters, but it is recommended to see the adapter's documentation
       to confirm its compatibility with this option.