Преглед на файлове

[docs] Fix some typographical errors (#1228)

Ayush Goyal преди 5 години
родител
ревизия
27e0109470

+ 1 - 1
docs/docs-site/content/administrator/administration/reference.md

@@ -22,7 +22,7 @@ In practice ~50 users / Hue peak time is the rule of thumb. This is accounting f
 
 ### General
 
-* Hue must be behing a load balancer proxying static files. e.g. NGINX is used for the containers, Cloudera Hue ships with HTTPD.
+* Hue must be behind a load balancer proxying static files. e.g. NGINX is used for the containers, Cloudera Hue ships with HTTPD.
 * Adding more Hue instances behind the load balancer will increase performances by 50 concurrent users.
 * Database backend should be such as MySql/Postgres/Oracle. Hue does not work on SQLite as it makes concurrent write calls to the database.
 * Check the number of documents in the Hue database. If they are too many (more than 100 000), delete the old records:

+ 1 - 1
docs/docs-site/content/administrator/configuration/server/_index.md

@@ -269,7 +269,7 @@ Configure Hue for SAML Authentication
 
 The Service Provider (Hue) and the Identity Provider use a metadata file to confirm each other's identity. Hue stores metadata from the SAML server, and the IdP stores metadata from Hue server.
 
-In Configure Hue at the Command Line, you must copy the metadata from your IdP's SAML server and store it in an XML file on every ost with a Hue server.
+In Configure Hue at the Command Line, you must copy the metadata from your IdP's SAML server and store it in an XML file on every host with a Hue server.
 Important: Read the documentation of your Identity Provider for details on how to procure the XML of the SAML server metadata.
 
 Configure Hue at the Command Line

+ 2 - 2
docs/docs-site/content/administrator/installation/cloud.md

@@ -11,7 +11,7 @@ To start a Hue instance:
 
     docker run -it -p 8888:8888 gethue/hue:latest
 
-In addition to providing to providing a ready to use image, the [Docker Guide](https://github.com/cloudera/hue/tree/testing/tools/docker) shows how to build it.
+In addition to providing a ready to use image, the [Docker Guide](https://github.com/cloudera/hue/tree/testing/tools/docker) shows how to build it.
 
 It then details how to start the containers and parameterize them.
 
@@ -132,7 +132,7 @@ This was a very basic introduction to metrics of Hue in the Kubernetes ecosystem
 
 ### Tracing
 
-Hue is getting easy to run with its Docker container and Kubernetes Helm package. Recent blog posts describes how to get access to logs and metrics. Even in a non distributed world it can get noisy to know how much time is being spent where in each user request.
+Hue is getting easy to run with its Docker container and Kubernetes Helm package. Recent blog posts describe how to get access to logs and metrics. Even in a non distributed world it can get noisy to know how much time is being spent where in each user request.
 
 Consequently, in the context of a Data Analyst, knowing why a certain query is slow can become problematic. On top of that, adding multiple tenants and users, and more than 20 external APIs and the fog about fine grain performances appears and its becomes extremely manual and time consuming to troubleshoot.
 

+ 1 - 1
docs/docs-site/content/developer/api/_index.md

@@ -19,7 +19,7 @@ communication calls.
 
 Hue is based on the Django Web Framework. Django comes with user authentication system. Django uses sessions and middleware to hook the authentication system into request object. Hue uses stock auth form which uses *username* and *password* and *csrftoken* form variables to authenticate.
 
-In this code snippet, we will use well-known python *requests* library. We will first acquire *csrftoken* by GET *login_url* and then create a dictionary of form data which contains *username*, *password* and *csrftoken* and the *next_url* and another dictionary for header which contains the *Referer* url and an empty dictionary for the cookies. After the POST request to *login_url* we will check the reponse code, which should be *r.status_code == 200*.
+In this code snippet, we will use well-known python *requests* library. We will first acquire *csrftoken* by GET *login_url* and then create a dictionary of form data which contains *username*, *password* and *csrftoken* and the *next_url* and another dictionary for header which contains the *Referer* url and an empty dictionary for the cookies. After the POST request to *login_url* we will check the response code, which should be *r.status_code == 200*.
 
 Once the request is successful then capture headers and cookies for subsequent requests. Subsequent *request.session* calls can be made by providing *cookies=session.cookies* and *headers=session.headers*.
 

+ 1 - 1
docs/docs-site/content/developer/connectors/_index.md

@@ -15,7 +15,7 @@ Connectors provide pluggable integration to any external data service so that an
 
 ### SqlAlchemy
 
-[SqlAlchemy](https://www.sqlalchemy.org) is the prefered way if the Hive API is not supported by the database. The core implementation is in [`sql_alchemy.py`](https://github.com/cloudera/hue/blob/master/desktop/libs/notebook/src/notebook/connectors/sql_alchemy.py) and relies on each repective SqlAlchemy dialect.
+[SqlAlchemy](https://www.sqlalchemy.org) is the prefered way if the Hive API is not supported by the database. The core implementation is in [`sql_alchemy.py`](https://github.com/cloudera/hue/blob/master/desktop/libs/notebook/src/notebook/connectors/sql_alchemy.py) and relies on each respective SqlAlchemy dialect.
 
 ### Hive Interface
 

+ 2 - 2
docs/docs-site/content/developer/development/_index.md

@@ -437,7 +437,7 @@ In a nutshell, front-end development is using:
 
 ### Javascript
 
-The javascript files are currently being migrated to webpack bundles, during this process some files will live under src/desktop/static/ and some will live under src/dekstop/js
+The javascript files are currently being migrated to webpack bundles, during this process some files will live under src/desktop/static/ and some will live under src/desktop/js
 
 For changes to the files under src/desktop/js the following applies:
 
@@ -517,7 +517,7 @@ Run the API unit tests
 
     ./build/env/bin/hue test unit
 
-Open a pull request which will automaticlly trigger a [CircleCi](https://circleci.com/gh/cloudera/hue) unit test run.
+Open a pull request which will automatically trigger a [CircleCi](https://circleci.com/gh/cloudera/hue) unit test run.
 
 How to run just some parts of the tests, e.g.:
 

+ 1 - 1
docs/docs-site/content/developer/parsers/_index.md

@@ -24,7 +24,7 @@ There are several parsers in Hue already (e.g. one for Impala, one for Hive..) a
 
 Building a dedicated work is more effort but it then allows a very rich end user experience, e.g.:
 
-* Handle invalid/imcomplete queries and propose suggestions/fixes
+* Handle invalid/incomplete queries and propose suggestions/fixes
 * date_column = <Date compatible UDF ...>
 * Language reference or data samples just by pointing the cursor on SQL identifiers
 * Leverage the parser for risk alerts (e.g. adding automatic LIMIT) or proper re-formatting

+ 3 - 3
docs/docs-site/content/user/querying/_index.md

@@ -105,7 +105,7 @@ If multiple tables appear in the FROM clause, including derived and joined table
 
 **Smart keyword completion**
 
-The autocompleter suggests keywords based on where the cursor is positioned in the statement. Where possible it will even suggest more than one word at at time, like in the case of IF NOT EXISTS, no one likes to type too much right? In the parts where order matters but the keywords are optional, for instance after FROM tbl, it will list the keyword suggestions in the order they are expected with the first expected one on top. So after FROM tbl the WHERE keyword is listed above GROUP BY etc.
+The autocompleter suggests keywords based on where the cursor is positioned in the statement. Where possible it will even suggest more than one word at a time, like in the case of IF NOT EXISTS, no one likes to type too much right? In the parts where order matters but the keywords are optional, for instance after FROM tbl, it will list the keyword suggestions in the order they are expected with the first expected one on top. So after FROM tbl the WHERE keyword is listed above GROUP BY etc.
 
 **Functions**
 
@@ -119,7 +119,7 @@ When editing subqueries it will only make suggestions within the scope of the su
 
 **Context popup**
 
-Right click on any fragement of the queries (e.g. a table name) to gets all its metadata information. This is a handy shortcut to get more description or check what types of values are contained in the table or columns.
+Right click on any fragment of the queries (e.g. a table name) to gets all its metadata information. This is a handy shortcut to get more description or check what types of values are contained in the table or columns.
 
 It’s quite handy to be able to look at column samples while writing a query to see what type of values you can expect. Hue now has the ability to perform some operations on the sample data, you can now view distinct values as well as min and max values. Expect to see more operations in coming releases.
 
@@ -660,7 +660,7 @@ The main advantage is to be able to add snippets of different dialects (e.g. PyS
 
 ![Notebook mode](https://cdn.gethue.com/uploads/2015/10/notebook-october.png)
 
-Any configured language of the Editor will be available as a dialect. Each snippet has a code editor, wih autocomplete, syntax highlighting and other feature like shortcut links to HDFS paths and Hive tables.
+Any configured language of the Editor will be available as a dialect. Each snippet has a code editor, with autocomplete, syntax highlighting and other feature like shortcut links to HDFS paths and Hive tables.
 
 ![Notebook Screen](https://cdn.gethue.com/uploads/2015/08/notebook.png)