From e5394cd91de634a7316e68d9394e23ef7129c5c8 Mon Sep 17 00:00:00 2001 From: Sofie Van Landeghem Date: Fri, 8 Jan 2021 09:39:47 +0100 Subject: [PATCH] fix small typos (#6698) --- website/docs/usage/layers-architectures.md | 4 ++-- website/docs/usage/training.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/website/docs/usage/layers-architectures.md b/website/docs/usage/layers-architectures.md index eb6f8b288..164ec15ba 100644 --- a/website/docs/usage/layers-architectures.md +++ b/website/docs/usage/layers-architectures.md @@ -716,7 +716,7 @@ that we want to classify as being related or not. As these candidate pairs are typically formed within one document, this function takes a [`Doc`](/api/doc) as input and outputs a `List` of `Span` tuples. For instance, the following implementation takes any two entities from the same document, as long as they -are within a **maximum distance** (in number of tokens) of eachother: +are within a **maximum distance** (in number of tokens) of each other: > #### config.cfg (excerpt) > @@ -742,7 +742,7 @@ def create_instances(max_length: int) -> Callable[[Doc], List[Tuple[Span, Span]] return get_candidates ``` -This function in added to the [`@misc` registry](/api/top-level#registry) so we +This function is added to the [`@misc` registry](/api/top-level#registry) so we can refer to it from the config, and easily swap it out for any other candidate generation function. diff --git a/website/docs/usage/training.md b/website/docs/usage/training.md index 58c846e9d..c0c3d1a9b 100644 --- a/website/docs/usage/training.md +++ b/website/docs/usage/training.md @@ -1029,7 +1029,7 @@ In this example we assume a custom function `read_custom_data` which loads or generates texts with relevant text classification annotations. Then, small lexical variations of the input text are created before generating the final [`Example`](/api/example) objects. The `@spacy.registry.readers` decorator lets -you register the function creating the custom reader in the `readers` +you register the function creating the custom reader in the `readers` [registry](/api/top-level#registry) and assign it a string name, so it can be used in your config. All arguments on the registered function become available as **config settings** – in this case, `source`.