RELEASE_NOTES

fsprojects · Jan 31, 2015 · 2dfa52d · 2dfa52d
1 parent 15d1813
commit 2dfa52d
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/RELEASE_NOTES.md b/RELEASE_NOTES.md
@@ -1,6 +1,6 @@
 #### 0.26.0 - 31.01.2015
 * Allow to opt-out of old frameworks in `paket.dependencies` - http://fsprojects.github.io/Paket/nuget-dependencies.html#Framework-restrictions
-* Allow `copy_local` settings in `paket.references` - http://fsprojects.github.io/Paket/references-files.html#copy_local
+* Allow `copy_local` settings in `paket.references` - http://fsprojects.github.io/Paket/references-files.html#copy_local-settings
 * COSMETICS: `paket.lock` beautification for HTTP specs - https://github.com/fsprojects/Paket/pull/571
 
 #### 0.25.0 - 25.01.2015

diff --git a/docs/content/references-files.md b/docs/content/references-files.md
@@ -28,7 +28,7 @@ For each MSBuild project alongside a `paket.references`, [`paket install`](paket
 
 The references injected into the MSBuild project reflect the complete set of rules specified within the package for each `lib` and `Content` item; each reference is `Condition`al on an MSBuild expression predicated on the project's active framework etc. This allows you to change the target version of the MSBuild project (either within Visual Studio or e.g. as part of a multi-pass build) without reinstalling dependencies or incurring an impenetrable set of diffs.
 
-### copy_local
+## copy_local settings
 
 It's possible to influence the `Private` property for references in project files: