summaryrefslogtreecommitdiff
path: root/deps/npm/html/doc/link.html
diff options
context:
space:
mode:
Diffstat (limited to 'deps/npm/html/doc/link.html')
-rw-r--r--deps/npm/html/doc/link.html6
1 files changed, 3 insertions, 3 deletions
diff --git a/deps/npm/html/doc/link.html b/deps/npm/html/doc/link.html
index 5ad8a8f581..72212661a6 100644
--- a/deps/npm/html/doc/link.html
+++ b/deps/npm/html/doc/link.html
@@ -24,7 +24,7 @@ symbolic link from <code>prefix/package-name</code> to the current folder.</p>
symlink from the local <code>node_modules</code> folder to the global symlink.</p>
<p>When creating tarballs for <code>npm publish</code>, the linked packages are
-"snapshotted" to their current state by resolving the symbolic links.</p>
+&quot;snapshotted&quot; to their current state by resolving the symbolic links.</p>
<p>This is
handy for installing your own stuff, so that you can work on it and test it
@@ -52,13 +52,13 @@ npm link ../node-redis # link the dir of your dependency</code></pre>
npm link redis</code></pre>
<p>That is, it first creates a global link, and then links the global
-installation target into your project's <code>node_modules</code> folder.</p>
+installation target into your project&#39;s <code>node_modules</code> folder.</p>
<h2 id="SEE-ALSO">SEE ALSO</h2>
<ul><li><a href="../doc/developers.html">developers(1)</a></li><li><a href="../doc/faq.html">faq(1)</a></li><li><a href="../doc/json.html">json(1)</a></li><li><a href="../doc/install.html">install(1)</a></li><li><a href="../doc/folders.html">folders(1)</a></li><li><a href="../doc/config.html">config(1)</a></li></ul>
</div>
-<p id="footer">link &mdash; npm@1.1.46</p>
+<p id="footer">link &mdash; npm@1.1.47</p>
<script>
;(function () {
var wrapper = document.getElementById("wrapper")