Merge pull request #6271 from walterhenry/develop-proof [ci skip]

This commit is contained in:
Ines Montani 2020-10-19 16:31:43 +02:00 committed by GitHub
commit b6b1c1e23c
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 2 additions and 2 deletions

View File

@ -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 Computing similarity scores can be helpful in many situations, but it's also
important to maintain **realistic expectations** about what information it can 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 "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 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: useful for your purpose. Here are some important considerations to keep in mind:

View File

@ -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 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 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 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.
</Infobox> </Infobox>