Merge pull request #2790 from szarnyasg/nits-20240428

Nits 20240428
duckdb · Apr 28, 2024 · 844b792 · 844b792
2 parents 0176827 + 4f1cb98
commit 844b792
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 7 deletions.
diff --git a/_posts/2024-04-02-duckplyr.md b/_posts/2024-04-02-duckplyr.md
@@ -1,6 +1,6 @@
 ---
 layout: post
-title: "duckplyr: dplyr powered by DuckDB"
+title: "duckplyr: dplyr Powered by DuckDB"
 author: Hannes Mühleisen
 avatar: "_site/images/team/hannes_muehleisen.jpg"
 thumb: "/images/blog/thumbs/240402.svg"

diff --git a/docs/extensions/spatial.md b/docs/extensions/spatial.md
@@ -286,7 +286,7 @@ Similarly there is a `.osm.pbf` replacement scan for `ST_ReadOsm`.
 
 ## Spatial Copy Functions
 
-Much like the `ST_Read` table function the spatial extension provides a GDAL based `COPY` function to export duckdb tables to different geospatial vector formats.
+Much like the `ST_Read` table function the spatial extension provides a GDAL based `COPY` function to export DuckDB tables to different geospatial vector formats.
 For example to export a table to a GeoJSON file, with generated bounding boxes, you can use the following query:
 
 ```sql

diff --git a/docs/sql/duckdb_table_functions.md b/docs/sql/duckdb_table_functions.md
@@ -80,7 +80,7 @@ The `duckdb_constraints()` function provides metadata about the constraints avai
 ## `duckdb_databases`
 
 The `duckdb_databases()` function lists the databases that are accessible from within the current DuckDB process.
-Apart from the database associated at startup, the list also includes databases that were [attached](statements/attach) later on to the duckdb process
+Apart from the database associated at startup, the list also includes databases that were [attached](statements/attach) later on to the DuckDB process
 
 | Column | Description | Type |
 |:-|:---|:-|

diff --git a/docs/sql/statements/create_type.md b/docs/sql/statements/create_type.md
@@ -23,8 +23,10 @@ CREATE TYPE x_index AS INTEGER;
 
 <div id="rrdiagram"></div>
 
-`CREATE TYPE` defines a new data type available to this duckdb instance. These new
-types can then be inspected in the `duckdb_types` table.
+The `CREATE TYPE` clause defines a new data type available to this DuckDB instance.
+These new types can then be inspected in the [`duckdb_types` table](../duckdb_table_functions#duckdb_types).
 
-Extending these custom types to support custom operators (such as the PostgreSQL `&&` operator)
-would require C++ development. To do this, create an [extension](../../extensions/overview).
+## Limitations
+
+Extending types to support custom operators (such as the PostgreSQL `&&` operator) is not possible via plain SQL.
+Instead, it requires adding additional C++ code. To do this, create an [extension](../../extensions/overview).