From b216ff43c971adc7ce0a49ec3ced3ec5b2dfd20d Mon Sep 17 00:00:00 2001
From: Preston Badeer <467756+pbadeer@users.noreply.github.com>
Date: Wed, 8 Jan 2020 09:49:40 -0600
Subject: [PATCH] Update vectors-similarity.md (#4889)

These links are broken on the website, due to quotes around the URLs.
---
 website/docs/usage/vectors-similarity.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/docs/usage/vectors-similarity.md b/website/docs/usage/vectors-similarity.md
index 0bb79779e..93ba67704 100644
--- a/website/docs/usage/vectors-similarity.md
+++ b/website/docs/usage/vectors-similarity.md
@@ -229,10 +229,10 @@ For more details on **adding hooks** and **overwriting** the built-in `Doc`,
 If you're using a GPU, it's much more efficient to keep the word vectors on the
 device. You can do that by setting the [`Vectors.data`](/api/vectors#attributes)
 attribute to a `cupy.ndarray` object if you're using spaCy or
-[Chainer]("https://chainer.org"), or a `torch.Tensor` object if you're using
-[PyTorch]("http://pytorch.org"). The `data` object just needs to support
+[Chainer](https://chainer.org), or a `torch.Tensor` object if you're using
+[PyTorch](http://pytorch.org). The `data` object just needs to support
 `__iter__` and `__getitem__`, so if you're using another library such as
-[TensorFlow]("https://www.tensorflow.org"), you could also create a wrapper for
+[TensorFlow](https://www.tensorflow.org), you could also create a wrapper for
 your vectors data.
 
 ```python