This is an automated email from the ASF dual-hosted git repository.
mck pushed a commit to branch cassandra-3.11
in repository https://gitbox.apache.org/repos/asf/cassandra.git
The following commit(s) were added to refs/heads/cassandra-3.11 by this push:
new 90d0857d34 fix typos in data modeling and getting started docs
90d0857d34 is described below
commit 90d0857d341a1735edfa9450c4488372b3b44f87
Author: Steve Putala <steve.put...@gmail.com>
AuthorDate: Mon Apr 17 22:18:58 2023 -0400
fix typos in data modeling and getting started docs
patch by Steve Putala; reviewed by Mick Semb Wever
ref: https://github.com/apache/cassandra/pull/2280
---
doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc | 2 +-
doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc | 2 +-
doc/modules/cassandra/pages/getting_started/production.adoc | 2 +-
3 files changed, 3 insertions(+), 3 deletions(-)
diff --git
a/doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc
b/doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc
index 21f9801812..ed40fb831f 100644
--- a/doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc
+++ b/doc/modules/cassandra/pages/data_modeling/data_modeling_queries.adoc
@@ -28,7 +28,7 @@ here, however, you’ll want to think not only from the customer
perspective in terms of how the data is written, but also in terms of
how the data will be queried by downstream use cases.
-You natural tendency as might be to focus first on designing the tables
+Your natural tendency might be to focus first on designing the tables
to store reservation and guest records, and only then start thinking
about the queries that would access them. You may have felt a similar
tension already when discussing the shopping queries before, thinking
diff --git a/doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc
b/doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc
index b478df14a1..2acd6cc2bf 100644
--- a/doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc
+++ b/doc/modules/cassandra/pages/data_modeling/data_modeling_rdbms.adoc
@@ -17,7 +17,7 @@ image::data_modeling_hotel_relational.png[image]
== Design Differences Between RDBMS and Cassandra
Let’s take a minute to highlight some of the key differences in doing
-ata modeling for Cassandra versus a relational database.
+data modeling for Cassandra versus a relational database.
=== No joins
diff --git a/doc/modules/cassandra/pages/getting_started/production.adoc
b/doc/modules/cassandra/pages/getting_started/production.adoc
index de7fb54234..93b26084b2 100644
--- a/doc/modules/cassandra/pages/getting_started/production.adoc
+++ b/doc/modules/cassandra/pages/getting_started/production.adoc
@@ -51,7 +51,7 @@ appropriate number of replicates, to ensure even token
allocation.
Read ahead is an operating system feature that attempts to keep as much
data as possible loaded in the page cache.
Spinning disks can have long seek times causing high latency, so additional
-throughout on reads using page cache can improve performance.
+throughput on reads using page cache can improve performance.
By leveraging read ahead, the OS can pull additional data into memory without
the cost of additional seeks.
This method works well when the available RAM is greater than the size of the
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
