kudu-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ale...@apache.org
Subject kudu git commit: [docs] fixed some typos
Date Wed, 22 Feb 2017 21:32:39 GMT
Repository: kudu
Updated Branches:
  refs/heads/master dc1e45a9a -> 07e55ed0b

[docs] fixed some typos

Change-Id: I5875e70962d1834a6dd3e168a7807c8073d4ea99
Reviewed-on: http://gerrit.cloudera.org:8080/6114
Reviewed-by: Jean-Daniel Cryans <jdcryans@apache.org>
Tested-by: Kudu Jenkins

Project: http://git-wip-us.apache.org/repos/asf/kudu/repo
Commit: http://git-wip-us.apache.org/repos/asf/kudu/commit/07e55ed0
Tree: http://git-wip-us.apache.org/repos/asf/kudu/tree/07e55ed0
Diff: http://git-wip-us.apache.org/repos/asf/kudu/diff/07e55ed0

Branch: refs/heads/master
Commit: 07e55ed0b93f13bab89c1f19c33e94add69edc00
Parents: dc1e45a
Author: Alexey Serbin <aserbin@cloudera.com>
Authored: Wed Feb 22 12:26:03 2017 -0800
Committer: Alexey Serbin <aserbin@cloudera.com>
Committed: Wed Feb 22 21:32:11 2017 +0000

 docs/administration.adoc      | 2 +-
 docs/export_control.adoc      | 2 +-
 docs/installation.adoc        | 2 +-
 docs/prior_release_notes.adoc | 6 +++---
 docs/quickstart.adoc          | 4 ++--
 docs/schema_design.adoc       | 4 ++--
 6 files changed, 10 insertions(+), 10 deletions(-)

diff --git a/docs/administration.adoc b/docs/administration.adoc
index 7323a19..d532561 100644
--- a/docs/administration.adoc
+++ b/docs/administration.adoc
@@ -223,7 +223,7 @@ WARNING: All of the command line steps below should be executed as the
   will be unavailable.
 . Decide how many masters to use. The number of masters should be odd. Three or five node
-  configurations are recommendeded; they can tolerate one or two failures respectively.
+  configurations are recommended; they can tolerate one or two failures respectively.
 . Perform the following preparatory steps for the existing master:
 * Identify and record the directory where the master's data lives. If using Kudu system packages,

diff --git a/docs/export_control.adoc b/docs/export_control.adoc
index e090f79..6c0815d 100644
--- a/docs/export_control.adoc
+++ b/docs/export_control.adoc
@@ -50,7 +50,7 @@ The following provides more details on the included cryptographic
 - This software uses OpenSSL to enable TLS-encrypted connections,
-  generate keys for assymetric cryptography, and generate and
+  generate keys for asymmetric cryptography, and generate and
   verify signatures using those keys.
 - This software uses Java SE Security libraries including the
   Java Secure Socket Extension (JSSE), Java Generic Security Service

diff --git a/docs/installation.adoc b/docs/installation.adoc
index 2f2199b..f1f1753 100644
--- a/docs/installation.adoc
+++ b/docs/installation.adoc
@@ -48,7 +48,7 @@ three tablet servers is necessary.
 .Operating System Requirements
     - RHEL 6, RHEL 7, CentOS 6, CentOS 7, Ubuntu 14.04 (Trusty), Ubuntu 16.04 (Xenial), Debian
8 (Jessie), or SLES 12.
-    - A kernel and fileystem that support _hole punching_. Hole punching is the use of the
+    - A kernel and filesystem that support _hole punching_. Hole punching is the use of the
       `fallocate(2)` system call with the `FALLOC_FL_PUNCH_HOLE` option set. See
       link:troubleshooting.html#req_hole_punching[troubleshooting hole punching] for more

diff --git a/docs/prior_release_notes.adoc b/docs/prior_release_notes.adoc
index 45b0b5e..727eb20 100644
--- a/docs/prior_release_notes.adoc
+++ b/docs/prior_release_notes.adoc
@@ -63,10 +63,10 @@ for a list of known issues and limitations.
 * The Java client now features client-side request tracing in order to help troubleshoot
   Error messages are now augmented with traces that show which servers were contacted before
-  timeout occured instead of just the last error. The traces also contain RPCs that were
+  timeout occurred instead of just the last error. The traces also contain RPCs that were
   required to fulfill the client's request, such as contacting the master to discover a tablet's
   location. Note that the traces are not available for successful requests and are not
-  programatically queryable.
+  programmatically queryable.
 == Optimizations and improvements
@@ -817,7 +817,7 @@ real-world use.
 - The master now attempts to spread tablets more evenly across the cluster during
 table creation. This has no impact on existing tables, but will improve the speed
-at which under-replicated tabletsare re-replicated after a tablet server failure.
+at which under-replicated tablets are re-replicated after a tablet server failure.
 - All licensing documents have been modified to adhere to ASF guidelines.

diff --git a/docs/quickstart.adoc b/docs/quickstart.adoc
index 0ed8245..42d9a2b 100644
--- a/docs/quickstart.adoc
+++ b/docs/quickstart.adoc
@@ -55,7 +55,7 @@ $ curl -s https://raw.githubusercontent.com/cloudera/kudu-examples/master/demo-v
 This command downloads a shell script which clones the `kudu-examples` Git repository and
 then downloads a VM image of about 1.2GB size into the current working
 directory.footnote:[In addition, the script will create a host-only network between host
-and guest and setup an enty in the `/etc/hosts` file with the name `quickstart.cloudera`
+and guest and setup an entry in the `/etc/hosts` file with the name `quickstart.cloudera`
 and the guest's IP address.] You can examine the script after downloading it by removing
 the `| bash` component of the command above. Once the setup is complete, you can verify
 that everything works by connecting to the guest via SSH:
@@ -87,7 +87,7 @@ to consult the <<trouble, Troubleshooting>> section.
 To practice some typical operations with Kudu and Impala, we'll use the
 https://data.sfgov.org/Transportation/Raw-AVL-GPS-data/5fk7-ivit/data[San Francisco MTA
 GPS dataset]. This dataset contains raw location data transmitted periodically from
-sensors installed on the busses in the SF MTA's fleet.
+sensors installed on the buses in the SF MTA's fleet.
 1. Download the sample data and load it into HDFS

diff --git a/docs/schema_design.adoc b/docs/schema_design.adoc
index bf42c50..14ddd29 100644
--- a/docs/schema_design.adoc
+++ b/docs/schema_design.adoc
@@ -292,7 +292,7 @@ independently.
 === Partitioning Examples
-To illustrate the factors and tradeoffs associated with designing a partitioning
+To illustrate the factors and trade-offs associated with designing a partitioning
 strategy for a table, we will walk through some different partitioning
 scenarios. Consider the following table schema for storing machine metrics data
 (using SQL syntax and date-formatted timestamps for clarity):
@@ -448,7 +448,7 @@ Number of Columns:: By default, Kudu will not permit the creation of tables
 more than 300 columns. We recommend schema designs that use fewer columns for best
-Size of Cells:: No individual cell may be larger than 64KB. The cells making up a
+Size of Cells:: No individual cell may be larger than 64KB. The cells making up
 a composite key are limited to a total of 16KB after the internal composite-key encoding
 done by Kudu. Inserting rows not conforming to these limitations will result in errors
 being returned to the client.

View raw message