diff --git a/DEVELOPER.md b/DEVELOPER.md
index 6e8a3bb..cbbb9f7 100644
--- a/DEVELOPER.md
+++ b/DEVELOPER.md
@@ -18,11 +18,11 @@ In NUnit Console you can just import projects from this directory and then run t
  
 ### Continuous Integration
 
-Project has a continuous integration flow being hosted by AppVeyor ([project page](https://ci.appveyor.com/project/oleg-nenashev/winsw)).
+Project has a continuous integration flow being hosted by AppVeyor ([project page](https://ci.appveyor.com/project/winsw/winsw)).
 This CI instance automates building and testing of the Release configuration of WinSW. 
 See [the appveyor.yml file](./appveyor.yml) for more details.
 
-Current status: [![Build status](https://ci.appveyor.com/api/projects/status/i94752yal9iy77in?svg=true)](https://ci.appveyor.com/project/oleg-nenashev/winsw)
+Versions generated by the CI instances are **NOT** aligned with the release version, they use a rolling version ID instead.
 
 ### Releasing to GitHub and NuGet
 
@@ -33,7 +33,7 @@ Here are the release steps:
 
 1. Integrate all pull requests you want to release to the master branch.
 2. Update [CHANGELOG](./CHANGELOG.md) and push changes to the master.
-3. Wait till the [AppVeyor build](https://ci.appveyor.com/project/oleg-nenashev/winsw) finishes for the last commit.
+3. Wait till the [AppVeyor build](https://ci.appveyor.com/project/winsw/winsw) finishes for the last commit.
 4. Go to the [winsw-release job page](https://ci.appveyor.com/project/oleg-nenashev/winsw-g2fwp).
 5. If you are doing a release with a new feature, bump the second digit in the _Version_ setting (e.g. to `2.N.${build}`) and change the next build number to `0`. In such case the version in assembly info will be `2.N.0`
 6. Run the [winsw-release](https://ci.appveyor.com/project/oleg-nenashev/winsw-g2fwp) build.