diff --git a/www/advanced-unix-installation.html b/www/advanced-unix-installation.html
index 6b4e7e0..51afae2 100644
--- a/www/advanced-unix-installation.html
+++ b/www/advanced-unix-installation.html
@@ -168,7 +168,7 @@
<a title="Sponsor: Druckerei" href="http://print24.com/de/">Druckerei</a><!-- 201110010720 -->
</div>
<div class="sponsor">
- <a title="Sponsor: Custom T-Shirts" href="http://www.ooshirts.com">Custom T-Shirts</a><!-- 2011050100030 ooshirts.com-->
+ <a title="Sponsor: alaTest.com" href="http://alatest.com">alaTest.com</a><!-- 20110801000300 -->
</div>
</div>
</div>
@@ -474,7 +474,7 @@
<p>While <kbd>configure</kbd> is designed to ease installation of ImageMagick, it often discovers problems that would otherwise be encountered later when compiling ImageMagick. The configure script tests for headers and libraries by executing the compiler (CC) with the specified compilation flags (CFLAGS), pre-processor flags (CPPFLAGS), and linker flags (LDFLAGS). Any errors are logged to the file <kbd>config.log</kbd>. If configure fails to discover a header or library please review this log file to determine why, however, please be aware that *errors in the <kbd>config.log</kbd> are normal* because configure works by trying something and seeing if it fails. An error in <kbd>config.log</kbd> is only a problem if the test should have passed on your system.</p>
<p>Common causes of configure failures are: 1) a delegate header is not in the header include path (CPPFLAGS -I option); 2) a delegate library is not in the linker search/run path (LDFLAGS -L/-R option); 3) a delegate library is missing a function (old version?); or 4) compilation environment is faulty.</p>
-<p>If all reasonable corrective actions have been tried and the problem appears be due to a flaw in the configure script, please send a bug report to the <a href="http://www.imagemagick.org/magick/viewforum.php?f=3">ImageMagick Defect Support Forum</a>. All bug reports should contain the operating system type (as reported by <kbd>uname -a</kbd>) and the compiler/compiler-version. A copy of the configure script output and/or the relevant portion of <kbd>config.log</kbd> file may be valuable in order to find the problem. If you post portions of <kbd>config.log</kbd>, please also send a script of the configure output and a description of what you expected to see (and why) so the failure you are observing can be identified and resolved.</p>
+<p>If all reasonable corrective actions have been tried and the problem appears be due to a flaw in the configure script, please send a bug report to the <a href="http://www.imagemagick.org/discourse-server/viewforum.php?f=3">ImageMagick Defect Support Forum</a>. All bug reports should contain the operating system type (as reported by <kbd>uname -a</kbd>) and the compiler/compiler-version. A copy of the configure script output and/or the relevant portion of <kbd>config.log</kbd> file may be valuable in order to find the problem. If you post portions of <kbd>config.log</kbd>, please also send a script of the configure output and a description of what you expected to see (and why) so the failure you are observing can be identified and resolved.</p>
<p>ImageMagick is now configured and ready to build</p>