Index: xdocs/using/managing-dependencies.xml
===================================================================
--- xdocs/using/managing-dependencies.xml	(revision 328913)
+++ xdocs/using/managing-dependencies.xml	(working copy)
@@ -115,10 +115,19 @@
         <p>
           Assuming that project is publishing a version called <code>SNAPSHOT</code> (which happens when the
           <code>jar:deploy-snapshot</code> goal is called), then each time you build Maven will check the remote
-          repository for changes in that JAR and download it again if a newer version is available.
+          repository for changes in that JAR and download it again if a newer <code>SNAPSHOT</code> is available.
         </p>
 
         <p>
+          <b>Note:</b> It seems to be a common misconception that Maven would
+          replace <code>SNAPSHOT</code> by the most current version of a project
+          that is available in the repository. This is not the case: using a
+          <code>SNAPSHOT</code> dependency requires that the project that you
+          depend on has actually published a <code>SNAPSHOT</code>,
+          and only this <code>SNAPSHOT</code> will get updated automatically.
+        </p>
+
+        <p>
           If you are working offline Maven will warn you that your SNAPSHOT dependencies may be out of date. This is
           just a warning, and as the remote copy often does not change frequently can be ignored.
         </p>