Remove dead links in XML comments to documentation

src/Castle.Windsor/MicroKernel/DefaultKernel.cs

@@ -516,7 +516,7 @@ public virtual bool HasComponent(Type serviceType)
 		///   Registers the components with the <see cref = "IKernel" />. The instances of <see cref = "IRegistration" /> are produced by fluent registration API. Most common entry points are
 		///   <see cref = "Component.For{TService}" /> method to register a single type or (recommended in most cases) <see cref = "Classes.FromAssembly(Assembly)" />. Let the Intellisense drive you through the
 		///   fluent
-		///   API past those entry points. For details see the documentation at http://j.mp/WindsorApi
+		///   API past those entry points.
 		/// </summary>
 		/// <example>
 		///   <code>kernel.Register(Component.For&lt;IService&gt;().ImplementedBy&lt;DefaultService&gt;().LifestyleTransient());</code>

src/Castle.Windsor/MicroKernel/IKernel.cs

@@ -198,7 +198,7 @@ IKernel AddFacility<T>(Action<T> onCreate)
 		///   Registers the components with the <see cref = "IKernel" />. The instances of <see cref = "IRegistration" /> are produced by fluent registration API.
 		///   Most common entry points are <see cref = "Component.For{TService}" /> method to register a single type or (recommended in most cases) 
 		///   <see cref = "Classes.FromAssembly(Assembly)" />.
-		///   Let the Intellisense drive you through the fluent API past those entry points. For details see the documentation at http://j.mp/WindsorApi
+		///   Let the Intellisense drive you through the fluent API past those entry points.
 		/// </summary>
 		/// <example>
 		///   <code>

src/Castle.Windsor/Windsor/Diagnostics/IUsingContainerAsServiceLocatorDiagnostic.cs

@@ -18,7 +18,7 @@ namespace Castle.Windsor.Diagnostics
 
 	/// <summary>
 	///   Detects components that are not extending Windsor's infrastructure yet depend on the container which usually means they use the container as service locator
-	///   which is a bad practice and should be avoided. Consult the documentation for more details: http://j.mp/WindsorSL
+	///   which is a bad practice and should be avoided.
 	/// </summary>
 	public interface IUsingContainerAsServiceLocatorDiagnostic : IDiagnostic<IHandler[]>
 	{

src/Castle.Windsor/Windsor/IWindsorContainer.cs

@@ -22,8 +22,7 @@ namespace Castle.Windsor
 	using Castle.Windsor.Installer;
 
 	/// <summary>
-	///   The <c>IWindsorContainer</c> interface exposes all the 
-	///   functionality the Windsor implements.
+	///   The <c>IWindsorContainer</c> interface exposes all the functionality that Windsor implements.
 	/// </summary>
 	public interface IWindsorContainer : IDisposable
 	{
@@ -84,7 +83,7 @@ IWindsorContainer AddFacility<TFacility>(Action<TFacility> onCreate)
 		IWindsorContainer GetChildContainer(string name);
 
 		/// <summary>
-		///   Runs the <paramref name = "installers" /> so that they can register components in the container. For details see the documentation at http://j.mp/WindsorInstall
+		///   Runs the <paramref name = "installers" /> so that they can register components in the container.
 		/// </summary>
 		/// <remarks>
 		///   In addition to instantiating and passing every installer inline you can use helper methods on <see
@@ -108,7 +107,7 @@ IWindsorContainer AddFacility<TFacility>(Action<TFacility> onCreate)
 		///   Registers the components with the <see cref = "IWindsorContainer" />. The instances of <see cref = "IRegistration" /> are produced by fluent registration API.
 		///   Most common entry points are <see cref = "Component.For{TService}" /> method to register a single type or (recommended in most cases) 
 		///   <see cref = "Classes.FromAssembly(Assembly)" />.
-		///   Let the Intellisense drive you through the fluent API past those entry points. For details see the documentation at http://j.mp/WindsorApi
+		///   Let the Intellisense drive you through the fluent API past those entry points.
 		/// </summary>
 		/// <example>
 		///   <code>

src/Castle.Windsor/Windsor/WindsorContainer.cs

@@ -410,7 +410,7 @@ public IWindsorContainer GetChildContainer(string name)
 		}
 
 		/// <summary>
-		///   Runs the <paramref name = "installers" /> so that they can register components in the container. For details see the documentation at http://j.mp/WindsorInstall
+		///   Runs the <paramref name = "installers" /> so that they can register components in the container.
 		/// </summary>
 		/// <remarks>
 		///   In addition to instantiating and passing every installer inline you can use helper methods on <see
@@ -464,7 +464,7 @@ public IWindsorContainer Install(params IWindsorInstaller[] installers)
 		///   Registers the components with the <see cref = "IWindsorContainer" />. The instances of <see cref = "IRegistration" /> are produced by fluent registration API.
 		///   Most common entry points are <see cref = "Component.For{TService}" /> method to register a single type or (recommended in most cases) 
 		///   <see cref = "Classes.FromAssembly(Assembly)" />.
-		///   Let the Intellisense drive you through the fluent API past those entry points. For details see the documentation at http://j.mp/WindsorApi
+		///   Let the Intellisense drive you through the fluent API past those entry points.
 		/// </summary>
 		/// <example>
 		///   <code>