Apply suggestions from code review

Co-authored-by: Gil Forsyth <[email protected]>

Author: cpcloud

ibis/backends/__init__.py

@@ -664,7 +664,7 @@ def create_catalog(self, name: str, /, *, force: bool = False) -> None:
         backend (where available), regardless of the terminology the backend uses.
 
         See the
-        [Table Heirarchy Concepts Guide](/concepts/backend-table-heirarchy.qmd)
+        [Table Hierarchy Concepts Guide](/concepts/backend-table-hierarchy.qmd)
         for more info.
         :::
 
@@ -690,7 +690,7 @@ def drop_catalog(self, name: str, /, *, force: bool = False) -> None:
         backend (where available), regardless of the terminology the backend uses.
 
         See the
-        [Table Heirarchy Concepts Guide](/concepts/backend-table-heirarchy.qmd)
+        [Table Hierarchy Concepts Guide](/concepts/backend-table-hierarchy.qmd)
         for more info.
         :::
 
@@ -720,7 +720,7 @@ def list_databases(
         backend (where available), regardless of the terminology the backend uses.
 
         See the
-        [Table Heirarchy Concepts Guide](/concepts/backend-table-heirarchy.qmd)
+        [Table Hierarchy Concepts Guide](/concepts/backend-table-hierarchy.qmd)
         for more info.
         :::
 
@@ -758,7 +758,7 @@ def create_database(
         backend (where available), regardless of the terminology the backend uses.
 
         See the
-        [Table Heirarchy Concepts Guide](/concepts/backend-table-heirarchy.qmd)
+        [Table Hierarchy Concepts Guide](/concepts/backend-table-hierarchy.qmd)
         for more info.
         :::
 
@@ -790,7 +790,7 @@ def drop_database(
         backend (where available), regardless of the terminology the backend uses.
 
         See the
-        [Table Heirarchy Concepts Guide](/concepts/backend-table-heirarchy.qmd)
+        [Table Hierarchy Concepts Guide](/concepts/backend-table-hierarchy.qmd)
         for more info.
         :::
 
@@ -1041,7 +1041,7 @@ def list_tables(
             (and catalog, if applicable for this backend) is used.
 
             See the
-            [Table Heirarchy Concepts Guide](/concepts/backend-table-heirarchy.qmd)
+            [Table Hierarchy Concepts Guide](/concepts/backend-table-hierarchy.qmd)
             for more info.
 
         Returns
@@ -1090,7 +1090,7 @@ def table(
             (and catalog, if applicable for this backend) is used.
 
             See the
-            [Table Heirarchy Concepts Guide](/concepts/backend-table-heirarchy.qmd)
+            [Table Hierarchy Concepts Guide](/concepts/backend-table-hierarchy.qmd)
             for more info.
 
         Returns
@@ -1109,13 +1109,13 @@ def table(
         >>> backend.table("foo")  # doctest: +SKIP
 
         Get the "foo" table from the "bar" database
-        (in duckdb's language they would say the "bar" schema,
+        (in DuckDB's language they would say the "bar" schema,
         in SQL this would be `"bar"."foo"`)
 
         >>> backend.table("foo", database="bar")  # doctest: +SKIP
 
         Get the "foo" table from the "bar" database, within the "baz" catalog
-        (in duckdb's language they would say the "bar" schema, and "baz" database,
+        (in DuckDB's language they would say the "bar" schema, and "baz" database,
         in SQL this would be `"baz"."bar"."foo"`)
 
         >>> backend.table("foo", database=("baz", "bar"))  # doctest: +SKIP