diff --git a/docs/data/json/json_type.md b/docs/data/json/json_type.md
index fbfef30a1a..043cb7735b 100644
--- a/docs/data/json/json_type.md
+++ b/docs/data/json/json_type.md
@@ -9,7 +9,7 @@ DuckDB supports `json` via the `JSON` logical type.
 The `JSON` logical type is interpreted as JSON, i.e., parsed, in JSON functions rather than interpreted as `VARCHAR`, i.e., a regular string (modulo the equality-comparison caveat at the bottom of this page).
 All JSON creation functions return values of this type.
 
-We also allow any of DuckDB's types to be casted to JSON, and JSON to be casted back to any of DuckDB's types, for example, to cast `JSON` to DuckDB's `STRUCT` type, run:
+We also allow any of DuckDB's types to be cast to JSON, and JSON to be cast back to any of DuckDB's types, for example, to cast `JSON` to DuckDB's `STRUCT` type, run:
 
 ```sql
 SELECT '{"duck": 42}'::JSON::STRUCT(duck INTEGER);
diff --git a/docs/sql/data_types/typecasting.md b/docs/sql/data_types/typecasting.md
index 0c10b4a21a..6c76931ab6 100644
--- a/docs/sql/data_types/typecasting.md
+++ b/docs/sql/data_types/typecasting.md
@@ -12,7 +12,7 @@ Explicit typecasting is performed by using a `CAST` expression. For example, `CA
 
 ## Implicit Casting
 
-In many situations, the system will add casts by itself. This is called *implicit* casting and happens, for example, when a function is called with an argument that does not match the type of the function but can be casted to the required type.
+In many situations, the system will add casts by itself. This is called *implicit* casting and happens, for example, when a function is called with an argument that does not match the type of the function but can be cast to the required type.
 
 Implicit casts can only be added for a number of type combinations, and is generally only possible when the cast cannot fail. For example, an implicit cast can be added from `INTEGER` to `DOUBLE` – but not from `DOUBLE` to `INTEGER`.