Fix typos

LICENSE-ScyllaDB-Source-Available.md

@@ -49,7 +49,7 @@ The terms "**You**" or "**Licensee**" refer to any individual accessing or using
 
 * **Ownership:** Licensor retains sole and exclusive ownership of all rights, interests and title in the Software and any scripts, processes, techniques, methodologies, inventions, know-how, concepts, formatting, arrangements, visual attributes, ideas, database rights, copyrights, patents, trade secrets, and other intellectual property related thereto, and all derivatives, enhancements, modifications and improvements thereof. Except for the limited license rights granted herein, Licensee has no rights in or to the Software and/ or Licensor’s trademarks, logo, or branding and You acknowledge that such Software, trademarks, logo, or branding is the sole property of Licensor.
 * **Feedback:** Licensee is not required to provide any suggestions, enhancement requests, recommendations or other feedback regarding the Software ("Feedback").  If, notwithstanding this policy, Licensee submits Feedback, Licensee understands and acknowledges that such Feedback is not submitted in confidence and Licensor assumes no obligation, expressed or implied, by considering it.  All right in any trademark or logo of Licensor or its affiliates and You shall make no claim of right to the Software or any part thereof to be supplied by Licensor hereunder and acknowledges that as between Licensor and You, such Software is the sole proprietary, title and interest in and to Licensor.such Feedback shall be assigned to, and shall become the sole and exclusive property of, Licensor upon its creation.
-* Except for the rights expressly granted to You under this Agreement, You are not granted any other licenses or rights in the Software or otherwise. This Agreement constitutes the entire agreement between you and the Licensor with respect to the subject matter hereof and supersedes all prior or contemporaneous communications, representations, or agreements, whether oral or written.
+* Except for the rights expressly granted to You under this Agreement, You are not granted any other licenses or rights in the Software or otherwise. This Agreement constitutes the entire agreement between You and the Licensor with respect to the subject matter hereof and supersedes all prior or contemporaneous communications, representations, or agreements, whether oral or written.
 * **Third-Party Software:** Customer acknowledges that the Software may contain open and closed source components (“OSS Components”) that are governed separately by certain licenses, in each case as further provided by Company upon request. Any applicable OSS Component license is solely between Licensee and the applicable licensor of the OSS Component and Licensee shall comply with the applicable OSS Component license.
 * If any provision of this Agreement is held to be invalid or unenforceable, such provision shall be struck and the remaining provisions shall remain in full force and effect.
 

docs/dev/isolation.md

@@ -23,7 +23,7 @@ The groups currently defined are:
 | gossip                                       | 1000
 | streaming (a.k.a maintenance)                | 200
 
-TODO: explain the purpose each of these scheduling groups, and what they are used for. E.g., "streaming" is also called maintenance and used also used for repair. memtable is used for memtable flushes (?). default is used for gossip, etc.
+TODO: explain the purpose of each of these scheduling groups, and what they are used for. E.g., "streaming" is also called maintenance and used also used for repair. memtable is used for memtable flushes (?). default is used for gossip, etc.
 
 The "Default shares" is the initial number of shares given to each scheduling group. They can be later modified by controllers, which aim to discover when a certain component needs to run faster because it is not keeping up - or run slower because it is finishing more quickly than it needs and causing performance to fluctuate. See the "Controllers" section below.
 

docs/dev/protocol-extensions.md

@@ -56,7 +56,7 @@ The keys and values are:
     is connected to (for example, `3`).
   - `SCYLLA_NR_SHARDS` is an integer containing the number of shards on this
     node (for example, `12`). All shard numbers are smaller than this number.
-  - `SCYLLA_PARTITIONER` is a fully-qualified name of the partitioner in use (i.e.
+  - `SCYLLA_PARTITIONER` is the fully-qualified name of the partitioner in use (i.e.
     `org.apache.cassandra.partitioners.Murmur3Partitioner`).
   - `SCYLLA_SHARDING_ALGORITHM` is the name of an algorithm used to select how
     partitions are mapped into shards (described below)

docs/dev/redis.md

@@ -91,7 +91,7 @@ name should be created (if not exists) or loaded.
 We known that, Redis allows us to store keys that map to any one of the
 basic data structures. Scylla supports variant type, which allows us to
 define one table to store all kind of these Redis data. For example ,we
-create the table with the scheme as follow:
+create the table with the schema as follow:
 
 ```
 CREATE TABLE redis （

tools/toolchain/README.md

@@ -35,7 +35,7 @@ The above command works as follows:
    container, so the same directory can be reused.
 3. The ":z" flag is necessary on systems with SELinux enabled, and causes a
    special selinux label to be applied to $HOME/.ccache so docker can write
-   it is. While this (rightfully) sounds fishy, note that dbuild already does
+   it. While this (rightfully) sounds fishy, note that dbuild already does
    the same thing to your current directory, where the build output is
    written - the current directory is also mounted with the ":z" flag.