diff --git a/programmer-guide/src/developing-applications.xml b/programmer-guide/src/developing-applications.xml
index 811e52a..df18510 100644
--- a/programmer-guide/src/developing-applications.xml
+++ b/programmer-guide/src/developing-applications.xml
@@ -899,17 +899,17 @@
 			    Making a dependency available for provisioning is simply a matter of copying it to the appropriate location in the
 			    @short.product.name@&rsquo;s local provisioning repository. By default this is
 			    <literal>SERVER_HOME/repository/usr</literal>. A more detailed discussion of the provisioning
-			    repository can be found in the <ulink url="../../user-guide/html/index.html">User Guide</ulink>.
+			    repository can be found in the <ulink url="../../virgo-user-guide/html/index.html">User Guide</ulink>.
 			</para>
 	    </section>
 	</section>
 	<section id="developing-applications-application-trace">
 		<title>Application trace</title>
 	    <para>
-		    As described in the <ulink url="../../user-guide/html/index.html">User Guide</ulink> @product.name@ provides support for
+		    As described in the <ulink url="../../virgo-user-guide/html/index.html">User Guide</ulink> @product.name@ provides support for
 		    per-application trace. @product.name@ provides SLF4J with Logback logging for Event Logging and Tracing. 
 		    Application trace is configured in the <literal>serviceability.xml</literal> file.
-		    See the <ulink url="../../user-guide/html/index.html">User Guide</ulink> for more details.
+		    See the <ulink url="../../virgo-user-guide/html/index.html">User Guide</ulink> for more details.
 		</para> 
     </section> 
        <section id="developing-applications-versioning">
diff --git a/programmer-guide/src/migrating-to-osgi.xml b/programmer-guide/src/migrating-to-osgi.xml
index 16f2c40..5378c0c 100644
--- a/programmer-guide/src/migrating-to-osgi.xml
+++ b/programmer-guide/src/migrating-to-osgi.xml
@@ -49,7 +49,7 @@
 			<para>
 				If you are not yet familiar with OSGi or simply want to deploy an existing web application on the @product.name@,
 				you can deploy a standard WAR and leverage the @short.product.name@ with a minimal learning curve. In fact reading the 
-				<ulink url="../../user-guide/html/index.html">@product.name@ User Guide</ulink>
+				<ulink url="../../virgo-user-guide/html/index.html">@product.name@ User Guide</ulink>
 				is pretty much all that you need to do to get started. Furthermore, you will gain
 				familiarity with the @product.name@, while preparing to take advantage of the other formats. 
 			</para>
diff --git a/programmer-guide/src/prerequisites.xml b/programmer-guide/src/prerequisites.xml
index 2813302..925cb57 100644
--- a/programmer-guide/src/prerequisites.xml
+++ b/programmer-guide/src/prerequisites.xml
@@ -18,7 +18,7 @@
 			To make effective use of the @product.name@, you should also refer to the following guides:
 		</para>
 		<itemizedlist>
-			<listitem><ulink url="../../user-guide/html/index.html">@project.name@ User Guide</ulink></listitem>
+			<listitem><ulink url="../../virgo-user-guide/html/index.html">@project.name@ User Guide</ulink></listitem>
 			<listitem><ulink url="http://static.springframework.org/osgi/docs/current/reference/html/">Spring Dynamic Modules Reference Guide</ulink></listitem>
 			<listitem><ulink url="http://static.springsource.org/spring/docs/3.0.x/spring-framework-reference/html/index.html">Spring Framework Reference Guide</ulink></listitem>
 		</itemizedlist>
diff --git a/user-guide/src/repository.xml b/user-guide/src/repository.xml
index 19aace5..cf4a473 100644
--- a/user-guide/src/repository.xml
+++ b/user-guide/src/repository.xml
@@ -18,7 +18,7 @@
 				Libraries are another example.  Some third-party dependencies consist of multiple bundles but are logically one unit.  To support this, the @product.name@ introduces the concept of a library.  A library is a collection of related bundles that can be referenced as a whole.  You typically express the dependencies between your application and third-party libraries using the <literal>Import-Package</literal>, <literal>Import-Bundle</literal>, or <literal>Import-Library</literal> manifest header in the <literal>MANIFEST.MF</literal> file of your application.  The <literal>Import-Package</literal> header is standard to OSGi; <literal>Import-Bundle</literal> and <literal>Import-Library</literal>, however, are specific to @product.name@.  
 			</para>
 			<para>
-				For additional details about the creation and usage of libraries, as well as general information about dependencies, see <ulink url="../../programmer-guide/html/index.html">Programmer&rsquo;s Guide</ulink>. 
+				For additional details about the creation and usage of libraries, as well as general information about dependencies, see <ulink url="../../virgo-programmer-guide/html/index.html">Programmer&rsquo;s Guide</ulink>. 
 			</para>
 			<para>
 				In @product.name@, you store all third-party dependencies required by your applications, such as Spring Framework and Hibernate, as artifacts in the provisioning repository.   As mentioned above, you can store the following types of artifacts in the repository: