6 files changed, 10 insertions, 10 deletions
diff --git a/BuildNotes2.txt b/BuildNotes2.txt
index 87673e57a8..2c000f6788 100644
--- a/BuildNotes2.txt
+++ b/BuildNotes2.txt
@@ -8,7 +8,7 @@ subsidiaries in the United States and other countries.
 Copyright (c) 2007 - 2011, Intel Corporation. All rights reserved.
 
 EDK II packages can be checked out from the following SVN address:
-http://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2 
+https://svn.code.sf.net/p/edk2/code/trunk/edk2
 
 The detailed introduction of these packages can be found in each package
 description file. (The *.dec file under the package directory)
@@ -124,7 +124,7 @@ Tools in Python
   long as you have the Python interpreter (version 2.5.4) installed. The source
   of Python code is locating at:
 
-    http://edk2-buildtools.svn.sourceforge.net/svnroot/edk2-buildtools/trunk/BaseTools
+    https://svn.code.sf.net/p/edk2-buildtools/code/trunk/BaseTools
 
   where:
 
diff --git a/DuetPkg/ReadMe.txt b/DuetPkg/ReadMe.txt
index 43f55294c0..3c4426733b 100644
--- a/DuetPkg/ReadMe.txt
+++ b/DuetPkg/ReadMe.txt
@@ -58,7 +58,7 @@ B. Build DUET image on Linux Platform
 
 	To build DUET image, Mingw GCC is required:
 	
-		1).  Check out build tools project from svn repository: https://buildtools.tianocore.org/svn/buildtools/trunk/BaseTools
+		1).  Check out build tools project from svn repository: https://svn.code.sf.net/p/edk2-buildtools/code/trunk/BaseTools
 		2).  Assume check out directory is /EDKII/BaseTools, enter /EDKII/BaseTools/gcc directory. Please refer to README.txt install all the necessary
 			 build packages following:
 			 * Python 2.5
diff --git a/EdkShellBinPkg/ReadMe.txt b/EdkShellBinPkg/ReadMe.txt
index 0064d0987f..29ba4d7a73 100644
--- a/EdkShellBinPkg/ReadMe.txt
+++ b/EdkShellBinPkg/ReadMe.txt
@@ -1,10 +1,10 @@
 The Ia32/Ipf/X64 binaries of EdkShellBinPkg are generated with EFI shell project (svn r63) and build with Edk Compatibility & BaseTools Package (r12898). The binaries are built with no debug information by building with "RELEASE" target.
 
 The following steps can help to re-generate these binaries for customization:
-1. Check out EdkCompatibilityPkg (r12898) to $(WORKSPACE)\EdkCompatibilityPkg (svn https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/EdkCompatibilityPkg).
-2. Check out EdkShellPkg (r12898) to $(WORKSPACE)\EdkShellPkg (svn https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/EdkShellPkg).
-3. Check out Edk Shell project source (r63) to $(WORKSPACE)\Shell (svn https://efi-shell.svn.sourceforge.net/svnroot/efi-shell/trunk/Shell). 
-4. Check out BaseTools (r12898) to $(WORKSPACE)\BaseTools (svn https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2/BaseTools).
+1. Check out EdkCompatibilityPkg (r12898) to $(WORKSPACE)\EdkCompatibilityPkg (svn https://svn.code.sf.net/p/edk2/code/trunk/edk2/EdkCompatibilityPkg).
+2. Check out EdkShellPkg (r12898) to $(WORKSPACE)\EdkShellPkg (svn https://svn.code.sf.net/p/edk2/code/trunk/edk2/EdkShellPkg).
+3. Check out Edk Shell project source (r63) to $(WORKSPACE)\Shell (svn https://svn.code.sf.net/p/efi-shell/code/trunk/Shell). 
+4. Check out BaseTools (r12898) to $(WORKSPACE)\BaseTools (svn https://svn.code.sf.net/p/edk2/code/trunk/edk2/BaseTools).
 5. Under $(WORKSPACE) directory (i.e. c:\EdkII),
    To generate Minimum Shell, execute: "build -a IA32 -a X64 -a IPF -p EdkShellPkg\EdkShellPkg.dsc -m Shell\Shell.inf -b RELEASE".
    To generate Full Shell, execute: "build -a IA32 -a X64 -a IPF -p EdkShellPkg\EdkShellPkg.dsc -m Shell\ShellFull.inf -b RELEASE".
diff --git a/EdkShellPkg/ReadMe.txt b/EdkShellPkg/ReadMe.txt
index 831aeb9b0a..c05ec8c36c 100644
--- a/EdkShellPkg/ReadMe.txt
+++ b/EdkShellPkg/ReadMe.txt
@@ -4,7 +4,7 @@ This is EDK style package and the following steps can help to build the package:
    https://efi-shell.tianocore.org/servlets/ProjectDocumentList?folderID=46&expandFolder=46&folderID=53
    
    Alternatively, the EDK Shell source directory can be retrieved from the following SVN address:
-   https://efi-shell.svn.sourceforge.net/svnroot/efi-shell/trunk/Shell
+   https://svn.code.sf.net/p/efi-shell/code/trunk/Shell
    SVN Revision r33 corresponds to Efi-Shell-Dev-Snapshot-20090527.zip development snapshot.
    
 2. Update EDK_SHELL_DIR macro in the [Defines] section in EdkShellPkg.dsc to point to
diff --git a/FatBinPkg/ReadMe.txt b/FatBinPkg/ReadMe.txt
index 434a0ffbae..d3d7b53127 100644
--- a/FatBinPkg/ReadMe.txt
+++ b/FatBinPkg/ReadMe.txt
@@ -1,5 +1,5 @@
 The binaries of FatBinPkg are generated with RELEASE_MYTOOLS from FatPkgDev Combo at the following SVN address: 
-http://edk2-fatdriver2.svn.sourceforge.net/svnroot/edk2-fatdriver2/trunk/Combo/FatPkgDev
+https://svn.code.sf.net/p/edk2-fatdriver2/code/trunk/Combo/FatPkgDev
 
 # Ebc, Ia32, Ipf, X64
   The binaries in this package currently are built from UDK2010.SR1 release: MdePkg and BaseTools (r12898), FatPkg (r67)
diff --git a/ShellBinPkg/ReadMe.txt b/ShellBinPkg/ReadMe.txt
index 144223ab23..6e975dc855 100644
--- a/ShellBinPkg/ReadMe.txt
+++ b/ShellBinPkg/ReadMe.txt
@@ -7,7 +7,7 @@ by building with "RELEASE" target.
 
 The following steps can help to re-generate these binaries for customization:
 1. Check out EDK II to $(WORKSPACE) 
-(svn https://edk2.svn.sourceforge.net/svnroot/edk2/trunk/edk2).
+(svn https://svn.code.sf.net/p/edk2/code/trunk/edk2).
 
 2. Under $(WORKSPACE) directory (i.e. c:\EdkII),
    To generate Shell, execute: