diff --git a/docs/administration.md b/docs/administration.md index 0ecbbed94..ee953e022 100644 --- a/docs/administration.md +++ b/docs/administration.md @@ -272,7 +272,7 @@ We currently track the following events - **ClearBit:** Count of cleared bits. - **ImportBit:** During a bulk data import this represents the count of bits created. - **SetRowAttrs:** Count of Attributes set per row. -- **SetColumnAttrs:** Count of Attributes set per collumn. +- **SetColumnAttrs:** Count of Attributes set per column. - **Bitmap:** Count of Bitmap queries. - **TopN:** Count of TopN queries. - **Union:** Count of Union queries. diff --git a/docs/configuration.md b/docs/configuration.md index 2d9d109b9..ce9d03203 100644 --- a/docs/configuration.md +++ b/docs/configuration.md @@ -117,7 +117,7 @@ The config file is in the [toml format](https://github.com/toml-lang/toml) and h #### Gossip Seeds -* Description: This specifies which internal host(s) should be used to initialize membership in the cluster. Typcially this can be the address of any available host in the cluster. For example, when starting a three-node cluster made up of `node0`, `node1`, and `node2`, the `gossip.seeds` for all three nodes can be configured to be the address of `node0`. Multiple seeds should be comma-separated in the flag and env forms. +* Description: This specifies which internal host(s) should be used to initialize membership in the cluster. Typically this can be the address of any available host in the cluster. For example, when starting a three-node cluster made up of `node0`, `node1`, and `node2`, the `gossip.seeds` for all three nodes can be configured to be the address of `node0`. Multiple seeds should be comma-separated in the flag and env forms. * Flag: `--gossip.seeds="localhost:11101"` * Env: `PILOSA_GOSSIP_SEEDS="localhost:11101"` * Config: @@ -399,7 +399,7 @@ The same cluster which uses HTTPS instead of HTTP can be configured as follows. ### Example Cluster Configuration (HTTPS, same host) -You can run a cluster on the same host using the configuration above with a few changes. Gossip port and bind adress should be different for each node and a data directory should be accessed only by a single node. +You can run a cluster on the same host using the configuration above with a few changes. Gossip port and bind address should be different for each node and a data directory should be accessed only by a single node. #### Node 0 @@ -444,7 +444,7 @@ You can run a cluster on the same host using the configuration above with a few [gossip] port = 12002 - seed = "locahost:12000" + seed = "localhost:12000" key = "/home/pilosa/private/gossip.key32" [cluster] diff --git a/docs/introduction.md b/docs/introduction.md index d2ebb4662..305c9680e 100644 --- a/docs/introduction.md +++ b/docs/introduction.md @@ -12,7 +12,7 @@ Pilosa is an open source, distributed bitmap index. [//]: # (TODO insert a graphic here?) -It is designed primarly for speed and horizontal scalability. If you have data with billions of objects that can have millions of possible attributes, and you want to explore those relationships, Pilosa can help you. +It is designed primarily for speed and horizontal scalability. If you have data with billions of objects that can have millions of possible attributes, and you want to explore those relationships, Pilosa can help you. "What attributes are the most common?", "Which objects have these specific attributes?", "What groups of attributes often appear together?" Pilosa is designed to answer these types of queries in real time, suitable for use with high rate data streams, or to power a user interface. diff --git a/docs/pdk.md b/docs/pdk.md index 4d1e599ad..a510f49f9 100644 --- a/docs/pdk.md +++ b/docs/pdk.md @@ -51,7 +51,7 @@ This JSON object would result in the following Pilosa schema: | location-state | | ranked | 100000 | | All frames are created as ranked frames by default, and fields are created with -a minmum size of zero and a fixed maximum of 2147483647. Fields at the top level +a minimum size of zero and a fixed maximum of 2147483647. Fields at the top level are created in the default frame. Frames are a dash-separated concatenation of all key values in the path - you can see this with frames like location-city. diff --git a/docs/tutorials.md b/docs/tutorials.md index 5539cedec..432c7466e 100644 --- a/docs/tutorials.md +++ b/docs/tutorials.md @@ -46,7 +46,7 @@ mkdir $HOME/pilosa-tls-tutorial && cd $_ Securing a Pilosa cluster consists of securing the communication between nodes using TLS and Gossip encryption. [Pilosa Enterprise](https://www.pilosa.com/enterprise/) additionally supports authentication and other security features, but those are not covered in this tutorial. -The first step is acquiring an SSL certificate. You can buy a commercial certificate or retrieve a Let's Encrypt certificiate but we will be using a self signed certificate for practical reasons. Using self-signed certificates is not recommended in production, since it makes man in the middle attacks easy. +The first step is acquiring an SSL certificate. You can buy a commercial certificate or retrieve a Let's Encrypt certificate but we will be using a self signed certificate for practical reasons. Using self-signed certificates is not recommended in production, since it makes man in the middle attacks easy. The following command creates a 2048bit self-signed wildcard certificate for `*.pilosa.local` which expires 10 years later.