Fix a URL (closing SF patch #462195).

Cleaned up a bunch of XXX comments containing links to additional
information, replacing them with proper references.
Replaced "MacOS" with "Mac OS", since that's what the style guide says.

Doc/inst/inst.tex

@@ -435,8 +435,7 @@ build.  Things to talk about:
 \subsubsection{Borland C++}
 
 This subsection describes the necessary steps to use Distutils with the 
-Borland \Cpp{} compiler version 5.5.\footnote{Check
-\url{http://www.borland.com/bcppbuilder/freecompiler/} for download}
+Borland \Cpp{} compiler version 5.5.
 %Should we mention that users have to create cfg-files for the compiler
 %see also http://community.borland.com/article/0,1410,21205,00.html 
 
@@ -478,7 +477,17 @@ If you want to use the Borland \Cpp{} compiler as default, you should
 consider to write it in your personal or system-wide configuration
 file for Distutils (see section~\ref{config-files}.)
  
-\XXX{One place to look: \url{http://www.cyberus.ca/~g_will/pyExtenDL.shtml}}
+\begin{seealso}
+  \seetitle[http://www.borland.com/bcppbuilder/freecompiler/]
+    {\Cpp{}Builder Compiler}
+    {Information about the free \Cpp{} compiler from Borland,
+     including links to the download pages.}
+
+  \seetitle[http://www.cyberus.ca/~g_will/pyExtenDL.shtml]
+    {Creating Python Extensions Using Borland's Free Compiler}
+    {Document describing how to use Borland's free command-line C++
+     compiler to build Python.}
+\end{seealso}
 
 
 \subsubsection{GNU C / Cygwin / MinGW32}
@@ -487,7 +496,7 @@ This section describes the necessary steps to use Distutils with the
 GNU C/\Cpp{} compilers in their Cygwin and MinGW32
 distributions.\footnote{Check
 \url{http://sources.redhat.com/cygwin/} and
-\url{http://www.mingw.org} for more information}
+\url{http://www.mingw.org/} for more information}
 
 \XXX{For a Python which was built with Cygwin, all should work without 
 any of these following steps.}
@@ -511,6 +520,7 @@ Then you can create from these information an import library for gcc.
 \begin{verbatim}
 dlltool --dllname python20.dll --def python20.def --output-lib libpython20.a
 \end{verbatim}
+
 The resulting library has to be placed in the same directory as 
 \file{python20.lib}. (Should be the \file{libs} directory under your
 Python installation directory.)
@@ -526,8 +536,9 @@ To let Distutils compile your extension with Cygwin you now have to type
 python setup.py build --compiler=cygwin
 \end{verbatim}
 
-and for Cygwin in no-cygwin mode\footnote{Then you have no POSIX emulation
-available, but you also don't need \file{cygwin1.dll}.} or for MinGW32 type
+and for Cygwin in no-cygwin mode\footnote{Then you have no
+\POSIX{} emulation available, but you also don't need
+\file{cygwin1.dll}.} or for MinGW32 type:
  
 \begin{verbatim}
 python setup.py build --compiler=mingw32
@@ -537,10 +548,17 @@ If you want to use any of these options/compilers as default, you should
 consider to write it in your personal or system-wide configuration file
 for Distutils (see section~\ref{config-files}.)
 
-\XXX{One place to look: \url{http://www.zope.org/Members/als/tips/win32_mingw_modules}}
+\begin{seealso}
+  \seetitle[http://www.zope.org/Members/als/tips/win32_mingw_modules]
+    {Building Python modules on MS Windows platform with MinGW32}
+    {Information about building the required libraries for the MinGW32
+     environment.}
 
-\XXX{For converted import libraries in cygwin/mingw32 and bcpp format,
-see \url{ftp://pyopengl.sourceforge.net/pub/pyopengl/win32-stuff/}.}
+  \seeurl{http://pyopengl.sourceforge.net/ftp/win32-stuff/}
+    {Converted import libraries in Cygwin/MinGW32 and Borland format,
+     and a script to create the registry entries needed for Distutils
+     to locate the built Python.}
+\end{seealso}
 
 
 \section{Alternate Installation}
@@ -772,7 +790,7 @@ python setup.py install --install-purelib=Site --install-platlib=Site
 The specified installation directories are relative to \filevar{prefix}.
 Of course, you also have to ensure that these directories are in
 Python's module search path, e.g. by putting a \file{.pth} file in
-\filevar{prefix} (\XXX{should have a section describing .pth files and
+\filevar{prefix} (\XXX{should have a section describing \file{.pth} files and
   cross-ref it here}).
 
 If you want to define an entire installation scheme, you just have to