From db24dc56145ff04dc6b4c4bc3e39e316b847ef17 Mon Sep 17 00:00:00 2001 From: walterhenry <55140654+walterhenry@users.noreply.github.com> Date: Mon, 19 Oct 2020 11:11:32 +0200 Subject: [PATCH] Proofread remarks I think these may the last remarks for the nightly docs. Only two minor things actually. --- website/docs/usage/101/_vectors-similarity.md | 2 +- website/docs/usage/visualizers.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/website/docs/usage/101/_vectors-similarity.md b/website/docs/usage/101/_vectors-similarity.md index cf5b70af2..c04198cb5 100644 --- a/website/docs/usage/101/_vectors-similarity.md +++ b/website/docs/usage/101/_vectors-similarity.md @@ -115,7 +115,7 @@ print(french_fries, "<->", burgers, french_fries.similarity(burgers)) Computing similarity scores can be helpful in many situations, but it's also important to maintain **realistic expectations** about what information it can -provide. Words can be related to each over in many ways, so a single +provide. Words can be related to each other in many ways, so a single "similarity" score will always be a **mix of different signals**, and vectors trained on different data can produce very different results that may not be useful for your purpose. Here are some important considerations to keep in mind: diff --git a/website/docs/usage/visualizers.md b/website/docs/usage/visualizers.md index 73b2d072d..cc73e7e67 100644 --- a/website/docs/usage/visualizers.md +++ b/website/docs/usage/visualizers.md @@ -257,7 +257,7 @@ output_path.open("w", encoding="utf-8").write(svg) Since each visualization is generated as a separate SVG, exporting `.svg` files only works if you're rendering **one single doc** at a time. (This makes sense – after all, each visualization should be a standalone graphic.) So instead of -rendering all `Doc`s at one, loop over them and export them separately. +rendering all `Doc`s at once, loop over them and export them separately.