diff --git a/website/docs/usage/models.mdx b/website/docs/usage/models.mdx index 52ce14e24..d7604a5d7 100644 --- a/website/docs/usage/models.mdx +++ b/website/docs/usage/models.mdx @@ -89,7 +89,7 @@ generic subclass containing only the base language data, can be found in To train a pipeline using the neutral multi-language class, you can set `lang = "xx"` in your [training config](/usage/training#config). You can also -import the `MultiLanguage` class directly, or call +\import the `MultiLanguage` class directly, or call [`spacy.blank("xx")`](/api/top-level#spacy.blank) for lazy-loading. ### Chinese language support {id="chinese",version="2.3"} diff --git a/website/docs/usage/rule-based-matching.mdx b/website/docs/usage/rule-based-matching.mdx index 4279aa212..54f4b51d8 100644 --- a/website/docs/usage/rule-based-matching.mdx +++ b/website/docs/usage/rule-based-matching.mdx @@ -413,8 +413,9 @@ you can also use an empty dictionary, `{}` as a wildcard representing **any token**. This is useful if you know the context of what you're trying to match, but very little about the specific token and its characters. For example, let's say you're trying to extract people's user names from your data. All you know is -that they are listed as "User name: {username}". The name itself may contain any -character, but no whitespace – so you'll know it will be handled as one token. +that they are listed as "User name: \{username\}". The name itself may contain +any character, but no whitespace – so you'll know it will be handled as one +token. ```python [{"ORTH": "User"}, {"ORTH": "name"}, {"ORTH": ":"}, {}] diff --git a/website/meta/universe.json b/website/meta/universe.json index b84449054..798a4e2a8 100644 --- a/website/meta/universe.json +++ b/website/meta/universe.json @@ -2943,7 +2943,7 @@ "", "print(doc._.clauses)", "# Output:", - "# ", + "# <SV, AE, died, None, None, None, [in Princeton, in 1955]>", "", "propositions = doc._.clauses[0].to_propositions(as_text=True)", "",