diff --git a/website/docs/usage/saving-loading.md b/website/docs/usage/saving-loading.md index c19ff39eb..968689baf 100644 --- a/website/docs/usage/saving-loading.md +++ b/website/docs/usage/saving-loading.md @@ -297,7 +297,7 @@ packages. This lets one application easily customize the behavior of another, by exposing an entry point in its `setup.py`. For a quick and fun intro to entry points in Python, check out [this excellent blog post](https://amir.rachum.com/blog/2017/07/28/python-entry-points/). -spaCy can load custom function from several different entry points to add +spaCy can load custom functions from several different entry points to add pipeline component factories, language classes and other settings. To make spaCy use your entry points, your package needs to expose them and it needs to be installed in the same environment – that's it. diff --git a/website/docs/usage/v3.md b/website/docs/usage/v3.md index 1024a2551..b0d9ca84c 100644 --- a/website/docs/usage/v3.md +++ b/website/docs/usage/v3.md @@ -395,7 +395,7 @@ type-check model definitions. For data validation, spaCy v3.0 adopts [`pydantic`](https://github.com/samuelcolvin/pydantic). It also powers the data validation of Thinc's [config system](https://thinc.ai/docs/usage-config), which -lets you to register **custom functions with typed arguments**, reference them +lets you register **custom functions with typed arguments**, reference them in your config and see validation errors if the argument values don't match.