From a080e047b7718ac1b6090ee848c7a0e577ebe2a8 Mon Sep 17 00:00:00 2001
From: Robin Winslow <robin@robinwinslow.co.uk>
Date: Sun, 21 Oct 2018 04:50:53 +0100
Subject: [PATCH] docs: Add a "d" to fix typo (#2672)

---
 website/docs/dependency-pinning.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/website/docs/dependency-pinning.md b/website/docs/dependency-pinning.md
index 4235e62deb..ed35116ec5 100644
--- a/website/docs/dependency-pinning.md
+++ b/website/docs/dependency-pinning.md
@@ -33,7 +33,7 @@ For example, you might have pinned `foobar` to version `1.1.0` and another autho
 
 ## Why pin dependencies?
 
-You mainly pin versions for certainty, an visibility. When you have a pinned version of each dependency in your `package.json`, you know exactly which version of each dependency is installed at any time. This benefits when upgrading versions as well as when rolling back in case of problems. Note: we'll cover lock files later, don't worry.
+You mainly pin versions for certainty, and visibility. When you have a pinned version of each dependency in your `package.json`, you know exactly which version of each dependency is installed at any time. This benefits when upgrading versions as well as when rolling back in case of problems. Note: we'll cover lock files later, don't worry.
 
 #### Upgrading pinned versions
 
-- 
GitLab