1. petsc
  2. PETSc
  3. petsc


Jed Brown  committed 7596b47

website: minor clean-up in developers and mailing list pages

  • Participants
  • Parent commits ca81866
  • Branches master

Comments (0)

Files changed (1)

File src/docs/website/developers/index.html

View file
  • Ignore whitespace
       <h2><a name="compiling_and_using_the_development_copy">Compiling and using the development copy (petsc-dev):</a></h2>
-      Use ./configure <a href="http://www.mcs.anl.gov/petsc/petsc-dev/docs/installation.html">to install PETSc</a>,
-      (trouble? please contact us petsc-maint@mcs.anl.gov). And subscribe to the
-      <a href="../miscellaneous/mailing-lists.html">petsc mailing lists</a>.
+      <p>
+        Use ./configure <a href="http://www.mcs.anl.gov/petsc/petsc-dev/docs/installation.html">to install PETSc</a>.
+        If you have problems, please use the <a href="../miscellaneous/mailing-lists.html">petsc-dev mailing list</a>).
+      </p>
       <h2><a name="building_documentation:">Building documentation:</a></h2>
           <a href="http://ftp.mcs.anl.gov/pub/sowing/sowing.tar.gz">Sowing</a>:
-          a text processing tool developed by bill gropp.</li>
+          a text processing tool developed by Bill Gropp.</li>
           <a href="http://ftp.mcs.anl.gov/pub/petsc/c2html.tar.gz">C2html</a>:
-          A version of pdflatex <a href="http://www.tug.org/teTeX/">(for example in teTeX)</a>:
+          A version of pdflatex <a href="http://www.tug.org/texlive/">(for example in TeX Live)</a>:
           This package might already be installed on most systems. It is required to generate
-          the users manual (part of the PETSc documentation)
+          the users manual (part of the PETSc documentation).
         use compilers specified to PETSc configure. [Windows users please install the corresponding
         cygwin packages]
-      <p>Once pdflatex (from teTeX) is in your PATH you can build the documentation with:</p>
+      <p>Once pdflatex (e.g., from <a href="http://tug.org/texlive">TeX Live</a>) is in your PATH, you can build the documentation with:</p>
         <li><code>make alldoc LOC=${PETSC_DIR}</code></li>
         <a href="https://bitbucket.org/petsc/petsc/wiki/Home">PETSc developer wiki</a>
         for detailed instructions on
         <a href="https://bitbucket.org/petsc/petsc/wiki/patch-instructions-git">
-        how to create a patch for PETSc using Git</a> or Mercurial.
+        how to create a patch for PETSc using Git</a>.