===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/30.html,v
retrieving revision 1.39
retrieving revision 1.40
diff -c -r1.39 -r1.40
*** www/30.html	2016/10/16 19:11:29	1.39
--- www/30.html	2017/06/26 17:18:57	1.40
***************
*** 77,83 ****
  <p>
  
  <li>A new packet filter, <a
! href="http://man.openbsd.org/?query=pf&sektion=4">PF</a>,
  featuring NAT capabilities, with a mostly ipf-compatible syntax.
  <p>
  
--- 77,83 ----
  <p>
  
  <li>A new packet filter, <a
! href="https://man.openbsd.org/?query=pf&sektion=4">PF</a>,
  featuring NAT capabilities, with a mostly ipf-compatible syntax.
  <p>
  
***************
*** 157,163 ****
  If you are planning on dual booting OpenBSD with another OS, you will need to read the included INSTALL.i386 document.
  
  <p>
! To make a boot floppy under MS-DOS, use the &quot;rawrite&quot; utility located at <i>CD:/3.0/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS, use the <a href="http://man.openbsd.org/?query=dd&sektion=1">dd(1)</a> utility. The following is an example usage of <a href="http://man.openbsd.org/?query=dd&sektion=1">dd(1)</a>, where the device could be &quot;floppy&quot;, &quot;rfd0c&quot;, or &quot;rfd0a&quot;.
  
  <ul><pre>
  # <strong>dd if=&lt;file&gt; of=/dev/&lt;device&gt; bs=32k</strong>
--- 157,163 ----
  If you are planning on dual booting OpenBSD with another OS, you will need to read the included INSTALL.i386 document.
  
  <p>
! To make a boot floppy under MS-DOS, use the &quot;rawrite&quot; utility located at <i>CD:/3.0/tools/rawrite.exe</i>. To make the boot floppy under a Unix OS, use the <a href="https://man.openbsd.org/?query=dd&sektion=1">dd(1)</a> utility. The following is an example usage of <a href="https://man.openbsd.org/?query=dd&sektion=1">dd(1)</a>, where the device could be &quot;floppy&quot;, &quot;rfd0c&quot;, or &quot;rfd0a&quot;.
  
  <ul><pre>
  # <strong>dd if=&lt;file&gt; of=/dev/&lt;device&gt; bs=32k</strong>
***************
*** 362,368 ****
  on most architectures (over 1200 packages build on i386, for instance).
  <p>
  The <i>ports/</i> directory represents a CVS (see the manpage for
! <a href="http://man.openbsd.org/?query=cvs&apropos=0&sektion=1&manpath=OpenBSD+Current&arch=i386&format=html">
  cvs(1)</a> if
  you aren't familiar with CVS) checkout of our ports.  As with our complete
  source tree, our ports tree is available via anoncvs.  So, in
--- 362,368 ----
  on most architectures (over 1200 packages build on i386, for instance).
  <p>
  The <i>ports/</i> directory represents a CVS (see the manpage for
! <a href="https://man.openbsd.org/?query=cvs&apropos=0&sektion=1&manpath=OpenBSD+Current&arch=i386&format=html">
  cvs(1)</a> if
  you aren't familiar with CVS) checkout of our ports.  As with our complete
  source tree, our ports tree is available via anoncvs.  So, in