Fix some typos (tableau#6)

website/docs/faq.md

@@ -7,7 +7,7 @@ Our team has a strong research background because Hyper originally started as a
 
 ## How is Hyper related to HyPer?
 
-Hyper started as a research project at [Technical University of Munich](https://db.in.tum.de/). Back then, the project was still called "HyPer", the "P" was lower-cased soon after the aquisition in 2016.
+Hyper started as a research project at [Technical University of Munich](https://db.in.tum.de/). Back then, the project was still called "HyPer", the "P" was lower-cased soon after the acquisition in 2016.
 You can still find find links to all the research paper on [HyPer's website](https://hyper-db.de/).
 The code base of Hyper is an evolution of the research project HyPer and many of the foundational papers of HyPer are still applicable.
 For more information on Hyper's journey, see [Our Journey](/journey)

website/docs/guides/sql_commands.md

@@ -13,7 +13,7 @@ with HyperProcess(telemetry=Telemetry.SEND_USAGE_DATA_TO_TABLEAU) as hyper:
                 ('dog', 4),
                 ('cat', 4),
                 ('bird', 2),
-                ('cangaroo', 2),
+                ('kangaroo', 2),
                 ('centipede', 100)
             """)
 
@@ -127,7 +127,7 @@ Escaping for identifiers and strings is documented in [General Syntax](../sql/sy
 Instead of reimplementing those escaping rules by yourself, you can use the `escape_name`
 and `escape_string_literal` functions to correctly format identifiers and strings in
 your SQL statements.
-Use `escape_name` for identifers, such as column or table names.
+Use `escape_name` for identifiers, such as column or table names.
 Use `escape_string_literal` when you need to use quoted string values.
 Furthermore, the utility classes `TableName` etc. are automatically escaped correctly when
 formatted as a string.

website/docs/hyper-api/hyper_process.md

@@ -176,7 +176,7 @@ database versions with the latest Hyper API and newer product versions
 but you cannot open them in older product versions. For example, the new
 database file format version `2` can be opened in Tableau Desktop
 2020.4.15 but it cannot be opened in Tableau Desktop 2020.3. The
-complete compatiblility matrix is documented in the version sections
+complete compatibility matrix is documented in the version sections
 below.
 :::
 

website/docs/sql/command/insert.md

@@ -132,7 +132,7 @@ To insert a row consisting entirely of default values:
 
     INSERT INTO films DEFAULT VALUES;
 
-To insert multiple rows using the multirow `VALUES` syntax:
+To insert multiple rows using the multi-row `VALUES` syntax:
 
     INSERT INTO films (code, title, did, date_prod, kind)
     VALUES

website/docs/sql/command/select.md

@@ -323,7 +323,7 @@ The `FROM` clause can contain the following elements:
     In Hyper, sub-queries can always access the attributes of preceding
     `FROM` items, even if the `LATERAL` keyword is not specified. As such,
     this keyword has no effect in Hyper and it is kept just for
-    compatibiliy reasons.
+    compatibility reasons.
 
 ### `WHERE` Clause {#where}
 

website/docs/sql/external/formats.md

@@ -13,7 +13,7 @@ The format of an external source is set through the
 `FORMAT` option. If the `FORMAT` option is not
 specified, Hyper will try to infer the format from the file extension.
 If multiple files are read, all have to possess the same extension for
-the inferral to succeed.
+the inference to succeed.
 
 The following formats are supported:
 
@@ -334,7 +334,7 @@ when using the Iceberg format:
 - Schema changes like added, dropped and renamed columns are supported
 
 :::note
-Hypers support for the Iceberg format is still in an early state and
+Hyper's support for the Iceberg format is still in an early state and
 should be considered experimental. We recommend to not use it in
 production workloads yet.
 :::

website/docs/sql/external/syntax.md

@@ -64,7 +64,7 @@ fill a products table:
 CREATE TABLE products AS (SELECT * FROM external('products.parquet'))
 ```
 
-## Creating External Tables vs. Using Ad-hoc Queryies
+## Creating External Tables vs. Using Ad-hoc Queries
 
 The set returning function `external` and the
 `CREATE TEMPORARY EXTERNAL TABLE` statement can both be used to query

website/docs/sql/scalar_func/conversion.md

@@ -10,7 +10,7 @@ TRY_CAST (<expression> AS <type>)
 
 The SQL `CAST` function converts a value from one type to another. If the
 type conversion fails, an error will be thrown.
-In constrast, the `TRY_CAST` function returns NULL if the conversion fails.
+In contrast, the `TRY_CAST` function returns NULL if the conversion fails.
 The syntax `::` is equivalent `CAST`.
 
 

website/docs/sql/scalar_func/datetime.md

@@ -20,7 +20,7 @@ date); we show only one of each such pair.
 The examples in this section that show `interval` values use a
 human-readable style similar to
 [PostgreSQL](https://www.postgresql.org/docs/current/datatype-datetime.html#INTERVAL-OUTPUT)
-to represent them as strings. However, when outputing interval data as a
+to represent them as strings. However, when outputting interval data as a
 string, Hyper uses the [ISO-8601
 style](https://en.wikipedia.org/wiki/ISO_8601#Time_intervals). An
 example of interval in this format is `P1DT2H3M4S`, which corresponds to
@@ -33,7 +33,7 @@ format than what is shown in this page.
 
 ## Operators
 
-Basic arithemtic operatos (`+`, `-`, `*`, `/`) are also available for dates, times and intervals.
+Basic arithmetic operators (`+`, `-`, `*`, `/`) are also available for dates, times and intervals.
 
 Operator|Example
 ---|---

website/docs/sql/syntax.md

@@ -69,7 +69,7 @@ on the command they are used in. Therefore they are sometimes simply
 called “names”.
 
 There are two types of identifiers: "unquoted" identifiers such as
-`Customers` and "quoted" or "delimitied" identifiers such as `"Discount"`.
+`Customers` and "quoted" or "delimited" identifiers such as `"Discount"`.
 
 Unquoted identifiers must start with a letter (non-Latin letters are
 also accepted) or an underscore. Subsequent characters in an identifier
@@ -79,10 +79,10 @@ Quoted identifiers are enclosed in double-quotes (`"`) and can contain
 arbitrary characters. Quoted identifiers can contain any character.
 To include a double quote, write two double quotes. Except for that,
 no escaping is required or supported. Special characters like tabs,
-protected whitespaces or even newline characters can be directly included
+protected whitespace or even newline characters can be directly included
 between the quotes.
 
-Unquoted indentifiers are always folded to lower case. For example, the identifiers
+Unquoted identifiers are always folded to lower case. For example, the identifiers
 `MyCustomers`, `myCustomers` and `"mycustomers"` all represent the lower-case
 name "mycustomers".
 In contrast, quoted not lower-cased and are case sensitive.
@@ -187,7 +187,7 @@ readable queries in such situations, Hyper provides another way, called “dolla
 to write string constants.
 
 A dollar-quoted string constant consists of a dollar sign (`$`), an optional “tag”
-of zeroor more characters, another dollar sign, an arbitrary sequence of characters
+of zero more characters, another dollar sign, an arbitrary sequence of characters
 that makes up the string content, a dollar sign, the same tag that began this dollar
 quote, and a dollar sign. For example, here are two different ways to specify the
 string “Dianne's horse” using dollar quoting:

website/docs/sql/window.md

@@ -170,7 +170,7 @@ The above query only shows the rows from the inner query having `rank`
 less than 3.
 
 When a query involves multiple window functions, it is possible to write
-out each one with a separate `OVER` clause, but this is duplicative and
+out each one with a separate `OVER` clause, but this is redundant and
 error-prone if the same windowing behavior is wanted for several
 functions. Instead, each windowing behavior can be named in a `WINDOW`
 clause and then referenced in `OVER`. For example:

website/sidebars.js

@@ -29,7 +29,7 @@ const sidebars = {
         'hyper-api/hyper_process',
         'hyper-api/connection',
         { type: 'link', label: "Examples", href: "https://github.com/tableau/hyper-api-samples" },
-        { type: 'link', label: "Python Referemce", href: "https://help.tableau.com/current/api/hyper_api/en-us/reference/py/index.html" },
+        { type: 'link', label: "Python Reference", href: "https://help.tableau.com/current/api/hyper_api/en-us/reference/py/index.html" },
         { type: 'link', label: "C++ Reference", href: "https://help.tableau.com/current/api/hyper_api/en-us/reference/cxx/index.html" },
         { type: 'link', label: ".NET Reference", href: "https://help.tableau.com/current/api/hyper_api/en-us/reference/dotnet/api/index.html" },
         { type: 'link', label: "Java Reference", href: "https://help.tableau.com/current/api/hyper_api/en-us/reference/java/overview-summary.html" },