From 906c226bdbd57ddc79a7b0d7152e20ef86479e7b Mon Sep 17 00:00:00 2001 From: Ned Western Date: Sat, 10 Feb 2024 11:36:26 +1100 Subject: [PATCH] Typo --- docs/user-guide/expressions/plugins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/expressions/plugins.md b/docs/user-guide/expressions/plugins.md index 8bfab6691c1e..1384eca05e29 100644 --- a/docs/user-guide/expressions/plugins.md +++ b/docs/user-guide/expressions/plugins.md @@ -204,7 +204,7 @@ class MyCustomExpr: ## Output data types -Output data types ofcourse don't have to be fixed. They often depend on the input types of an expression. To accommodate +Output data types of course don't have to be fixed. They often depend on the input types of an expression. To accommodate this you can provide the `#[polars_expr()]` macro with an `output_type_func` argument that points to a function. This function can map input fields `&[Field]` to an output `Field` (name and data type).