diff --git a/bochs/doc/docbook/development/development.dbk b/bochs/doc/docbook/development/development.dbk
index 71941356b..1d841efc9 100644
--- a/bochs/doc/docbook/development/development.dbk
+++ b/bochs/doc/docbook/development/development.dbk
@@ -71,7 +71,7 @@ SF username and type your password.
$ svn update file.cc
$ svn commit --username sfusername file.cc
[editor opens. type log message, save, and exit.]
- Login area: <https://bochs.svn.sourceforge.net:443> SourceForge Subversion area
+ Login area: <https://svn.code.sf.net:443> SourceForge Subversion area
Username: sfusername
Password for 'sfusername': <--type your password
Sending file.cc
@@ -2328,7 +2328,7 @@ Do a clean SVN checkout from the release tag and specify a not yet existing
directory name with the version number as the destination. Then create the
source package from this new directory.
- svn co https://svn.code.sf.net/p/bochs/code/tags/REL_2_5_FINAL/bochs bochs-2.5
+ svn co http://svn.code.sf.net/p/bochs/code/tags/REL_2_5_FINAL/bochs bochs-2.5
tar czvf bochs-2.5.tar.gz --exclude=.svn bochs-2.5
The source TAR file bochs-2.5.tar.gz is ready for upload.
diff --git a/bochs/doc/docbook/user/user.dbk b/bochs/doc/docbook/user/user.dbk
index a61d3ea8c..3f3a919af 100644
--- a/bochs/doc/docbook/user/user.dbk
+++ b/bochs/doc/docbook/user/user.dbk
@@ -861,7 +861,7 @@ to mention, running DOOM, though at then-pathetic speeds.
The change log is stored in the Bochs source code in a file called
-CHANGES. Click here
+CHANGES. Click here
to see the latest version of the CHANGES file.
@@ -1114,7 +1114,7 @@ below.
You can also use the SVN checkout command to get the Bochs source code for
any release since March 2000. The command is
- user$ svn co https://bochs.svn.sourceforge.net/svnroot/bochs/tags/tagname bochs
+ user$ svn co http://svn.code.sf.net/p/bochs/code/tags/tagname/bochs bochs
The tagname tells which release you want, and it can be one of the following: