From 7ba06ee944df08fa8befbfc58d8bc641f5e8d278 Mon Sep 17 00:00:00 2001 From: ND Date: Wed, 23 Mar 2022 22:19:32 +0100 Subject: [PATCH] Correcting some typos (#19338) Co-authored-by: Andreas Burner --- docs/docs/contributing/hooks-and-linting.mdx | 2 +- docs/docs/installation/configuring-superset.mdx | 2 +- docs/docs/installation/sql-templating.mdx | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/docs/contributing/hooks-and-linting.mdx b/docs/docs/contributing/hooks-and-linting.mdx index dc8cfef0dc..8539ecb6b2 100644 --- a/docs/docs/contributing/hooks-and-linting.mdx +++ b/docs/docs/contributing/hooks-and-linting.mdx @@ -39,7 +39,7 @@ We use [Pylint](https://pylint.org/) for linting which can be invoked via: tox -e pylint ``` -In terms of best practices please advoid blanket disablement of Pylint messages globally (via `.pylintrc`) or top-level within the file header, albeit there being a few exceptions. Disablement should occur inline as it prevents masking issues and provides context as to why said message is disabled. +In terms of best practices please avoid blanket disablement of Pylint messages globally (via `.pylintrc`) or top-level within the file header, albeit there being a few exceptions. Disablement should occur inline as it prevents masking issues and provides context as to why said message is disabled. Additionally, the Python code is auto-formatted using [Black](https://github.com/python/black) which is configured as a pre-commit hook. There are also numerous [editor integrations](https://black.readthedocs.io/en/stable/integrations/editors.html) diff --git a/docs/docs/installation/configuring-superset.mdx b/docs/docs/installation/configuring-superset.mdx index 4c504e8c8c..97038e84c0 100644 --- a/docs/docs/installation/configuring-superset.mdx +++ b/docs/docs/installation/configuring-superset.mdx @@ -10,7 +10,7 @@ version: 1 ### Configuration To configure your application, you need to create a file `superset_config.py` and add it to your -`PYTHONPATH`. If your applcation was installed using docker-compose an alternative configuration is required. See [https://github.com/apache/superset/tree/master/docker#readme](https://github.com/apache/superset/tree/master/docker#readme) for details. +`PYTHONPATH`. If your application was installed using docker-compose an alternative configuration is required. See [https://github.com/apache/superset/tree/master/docker#readme](https://github.com/apache/superset/tree/master/docker#readme) for details. Here are some of the parameters you can set in that file: ``` diff --git a/docs/docs/installation/sql-templating.mdx b/docs/docs/installation/sql-templating.mdx index 8bb419ca12..40f0744fba 100644 --- a/docs/docs/installation/sql-templating.mdx +++ b/docs/docs/installation/sql-templating.mdx @@ -120,7 +120,7 @@ In this section, we'll walkthrough the pre-defined Jinja macros in Superset. The `{{ current_username() }}` macro returns the username of the currently logged in user. If you have caching enabled in your Superset configuration, then by default the the `username` value will be used -by Superset when calculating the cache key. A cache key is a unique identifer that determines if there's a +by Superset when calculating the cache key. A cache key is a unique identifier that determines if there's a cache hit in the future and Superset can retrieve cached data. You can disable the inclusion of the `username` value in the calculation of the @@ -134,8 +134,8 @@ cache key by adding the following parameter to your Jinja code: The `{{ current_user_id() }}` macro returns the user_id of the currently logged in user. -If you have caching enabled in your Superset configuration, then by defaul the the `user_id` value will be used -by Superset when calculating the cache key. A cache key is a unique identifer that determines if there's a +If you have caching enabled in your Superset configuration, then by default the the `user_id` value will be used +by Superset when calculating the cache key. A cache key is a unique identifier that determines if there's a cache hit in the future and Superset can retrieve cached data. You can disable the inclusion of the `user_id` value in the calculation of the