Merge pull request #708 from NReilingh/patch-3

corrected missing link

NuGet.Docs/ndocs/Schema/project.json.md

@@ -47,7 +47,7 @@ The Package id corresponds to the id of the package on nuget.org , the same as t
 
 The version constraint of **"5.0.0"** corresponds to the **>= 5.0.0** constraint. This means that if for some reason 5.0.0 is not available on the server and 5.0.1 is, the restore will pick 5.0.1 and warn you about the upgrade. Otherwise restore will pick the lowest possible version on the server matching the constraint which will be 5.0.0. 
 
-See [dependency resolution document]() for more details on resolution rules. 
+See [dependency resolution document](../consume-packages/dependency-resolution) for more details on resolution rules. 
 
 ## Frameworks
 
@@ -116,4 +116,4 @@ Note that it is possible to edit the file, the user is responsible to build the
 The `project.lock.json` file is generated in the process of restoring the NuGet packages in projects that use `project.json`. It holds a snapshot of all the information that is generated as NuGet walks the graph of packages and includes the version, contents, and dependencies of all the packages in your project. The build system uses this to choose packages from a global location that are relevant when building the project instead of depending on a local packages folder in the project itself. This results in faster build performance because it's necessary to read only `project.lock.json` instead of many separate `.nuspec` files.
 
 The `project.lock.json` is automatically generated on package restore, so it can be omitted from source control by adding it to `.gitignore` and `.tfignore` files. However, if you include it in source control, the change history will show changes in dependencies resolved over time. 
-
+