Commits

Shlomi Fish  committed 67c8d66

Spell checked more.

  • Participants
  • Parent commits 3522216

Comments (0)

Files changed (8)

File bin/spell-checker-iface.sh

 #!/bin/bash
 find dest/t2-homepage/ -name '*.html' -or -name '*.xhtml' |
     ( LC_ALL=C sort  ) |
-    perl -lne 'print if 1..m#philosophy/computers/education/opinion-on-the-technion#' |
+    perl -lne 'print if 1..m#philosophy/computers/high-quality-software/what-makes-software-high-quality/ways-to-achieve-quality#' |
     grep -vP 'guide2ee/undergrad' |
     grep -vP '(?:humour/TheEnemy/(?:The-Enemy-(?:English-)?rev|TheEnemy))' |
     grep -vP '(?:humour/by-others/(?:English-is-a-Crazy-Language|darien|hitchhiker|how-many-newsgroup-readers|oded-c|s-stands-for-simple|technion-bit-1|top-12-things-likely|was-the-death-star-attack|grad-student-jokes-from-jnoakes))' |
     grep -vP 'humour/human-hacking/hebrew-v2' |
     grep -vP 'humour/humanity/ongoing-text-hebrew' |
     grep -vP 'lecture/Lambda-Calculus/slides/shriram\.scm' |
+    grep -vP 'dest/t2-homepage/philosophy/computers/high-quality-software/what-makes-software-high-quality' |
     xargs perl bin/html-check-spelling-xmlp.pl |
     grep ':'
     # perl -lne 'print if /MathVentures\/3d.*\.xhtml/' |

File lib/docbook/4/xml/case-for-file-swapping-rev3.xml

             mantras of: “You’re stealing someone else’s (intellectual) property
             so you are a criminal.” or “You’re violating the law so you are
             a criminal.”, etc. It was obvious that their cognition was
-            contaminated with the mis-interpretations of these terms, which
+            contaminated with the misinterpretations of these terms, which
             caused their thoughts and speech to be mutilated as well.
         </para>
         <para>

File lib/docbook/4/xml/foss-licences-wars.xml

                 <date>21 August 2009</date>
                 <authorinitials>shlomif</authorinitials>
                 <revremark>
-                    Fixed some small typos and mis-phrasings.
+                    Fixed some small typos and misphrasings.
                 </revremark>
             </revision>
 

File lib/docbook/4/xml/perfect-it-workplace.xml

                     <ulink url="http://better-scm.shlomifish.org/">state-of-the-art
                         version control system</ulink> , of which there are
                     currently several high-quality open-source alternatives.
-                    Some very costy version control systems have a bad
+                    Some very costly version control systems have a bad
                     reputation for being extreme troublemakers, while the
                     modern open-source alternatives "just work".
                 </para>
                     something good, you'll have to pay more.", often cheaper,
                     or even gratis (or open-source) solutions are more
                     powerful (not to mention more reliable and faster) than
-                    their more costy counterparts.
+                    their more costly counterparts.
                 </para>
                 <para>
                     Often, however, the really good solutions will be an

File lib/docbook/4/xml/what-makes-software-high-quality-rev2.xml

                 <authorinitials>shlomif</authorinitials>
                 <revremark>
                     Changed “a software” to something more idiomatic,
-                    and fixed a mis-phrasing towards the beginning.
+                    and fixed a bad phrasing towards the beginning.
                 </revremark>
             </revision>
             <revision>
                     introduction. Placed the Intro FCS story in the
                     “Motivation” section. Added the “organisation” sub-section
                     to the Intro.  Added the note about the generic “weight
-                    function”.  Aded a link to “The Stanford Checker”.
+                    function”.  Added a link to “The Stanford Checker”.
                     Corrected many “a software” instances. Added the note about
                     how Linux and Windows looked to the Aesthetics.  Added the
                     note about low-quality code and organisational quality to
                     Using a pure-public-domain licensing terms for your
                     software is problematic because not all countries have a
                     concept of “public-domain”, similar to that of the United
-                    States, because many people mis-interpret it, and because
+                    States, because many people misinterpret it, and because
                     it is not clear whether software can be licensed under the
                     public-domain to begin with. (And other such issues).
                 </para>
             to use than urpmi, when I have to work on Ubuntu.
         </para>
         <para>
-            Back to more visual aesthics, one of the reasons that made me
+            Back to more visual aesthetics, one of the reasons that made me
             want to use Linux more than Windows 95’ or 98’ was the fact that
             its desktops were truly themable and could be made to look much
             better without effort. If I got tired of the same look, I could
             <ulink url="http://youtube.com/watch?v=xC5uEe5OzNQ">effects
                 supplied by the Linux 3-D desktops</ulink>, which
             have put the 9-milliard Dollar effects of Vista to shame,
-            have convinced some people to install Linux on their comptuer
-            aftern seeing them.
+            have convinced some people to install Linux on their computer
+            after seeing them.
         </para>
     </section>
     <section id="quality-parameters-conclusion">
                     <listitem>
                         <para>
                             Some solvers are binary-only and only run on
-                            DOS or Windows. Open-source commandline ones
+                            DOS or Windows. Open-source command-line ones
                             may probably perform better on Linux or other Unix
                             systems.
                         </para>
             <ulink url="http://perltraining.com.au/">Perl Training Australia</ulink>,
             who gave some very useful comments on the first and second
             revisions, and to “Limbic_Region”, for noting an
-            ommission from it. Thanks to many people on the IRC
+            omission from it. Thanks to many people on the IRC
             (= Internet Relay Chat) who have read the article and commented,
             and chose not to be explicitly credited.
         </para>

File lib/docbook/4/xml/what-makes-software-high-quality.xml

                 <authorinitials>shlomif</authorinitials>
                 <revremark>
                     Changed "a software" to something more idiomatic,
-                    and fixed a mis-phrasing towards the beginning.
+                    and fixed a bad phrasing towards the beginning.
                 </revremark>
             </revision>
         </revhistory>
                     Using a pure-public-domain Licence for your software is
                     problematic because not all countries have a concept of
                     "public-domain", similar to that of the United States,
-                    because many people mis-interpret it, and because
+                    because many people misinterpret it, and because
                     it is not clear whether software can be licensed under
                     the public-domain to begin with. (And other such issues).
                 </para>
             one: PHP 4 was not compatible with PHP 3 and PHP 5 was not
             compatible with PHP 4. Furthermore, sometimes existing user-land
             code was broken in minor-digit releases. As such maintaining
-            PHP code into the future is a very costy process, especially if
+            PHP code into the future is a very costly process, especially if
             you want it to work with a range of versions.
         </para>
         <para>
             pleasing. Aesthetics in this context, does not necessarily mean
             very "artsy" or having a breath-taking style. But we may have
             run into software (usually one for internal use or one
-            of those very costy, bad-quality, niche, software) that seemed
+            of those very costly, bad-quality, niche, software) that seemed
             very ugly and badly designed, with a horrible user-interface,
             etc.
         </para>

File lib/hunspell/whitelist1.txt

 Whatsup
 Yegge's
 zsh
+
+====dest/t2-homepage/philosophy/computers/high-quality-software/index.html,dest/t2-homepage/philosophy/computers/high-quality-software/rev2/index.html,dest/t2-homepage/philosophy/computers/high-quality-software/rev2/what-makes-software-high-quality-rev2/about.html,dest/t2-homepage/philosophy/computers/high-quality-software/rev2/what-makes-software-high-quality-rev2/freecell-solvers-quality.html,dest/t2-homepage/philosophy/computers/high-quality-software/rev2/what-makes-software-high-quality-rev2/index.html,dest/t2-homepage/philosophy/computers/high-quality-software/rev2/what-makes-software-high-quality-rev2/parameters-of-quality.html,dest/t2-homepage/philosophy/computers/high-quality-software/rev2/what-makes-software-high-quality-rev2/ways-to-achieve-quality.html,dest/t2-homepage/philosophy/computers/high-quality-software/what-makes-software-high-quality/about.html,dest/t2-homepage/philosophy/computers/high-quality-software/what-makes-software-high-quality/freecell-solvers-quality.html,dest/t2-homepage/philosophy/computers/high-quality-software/what-makes-software-high-quality/index.html,dest/t2-homepage/philosophy/computers/high-quality-software/what-makes-software-high-quality/parameters-of-quality.html,dest/t2-homepage/philosophy/computers/high-quality-software/what-makes-software-high-quality/ways-to-achieve-quality.html
+
+0B
+386BSD
+admins
+AIX
+Alt
+AmigaOS
+apps
+artsy
+Autotools
+BeOS
+bolds
+CADs
+ccna
+Certkiller
+cisco
+CMS
+COM
+Corp
+CPANPLUS
+CPython
+CreateProcess
+CRMC
+C-struct
+Ctrl
+CVSNT
+dat
+Digg
+DLL
+DocBook-4
+DOSBox
+ESC
+EULAs
+F1
+FCELL
+FCPro
+FCS
+FC-S-Comp
+fc-solve
+fc-solve-discuss
+featureful
+firefox
+firefox-gnome-support
+freecell_solver_
+GCC's
+GHC
+gvim
+Hah
+having_good_code
+Holroyd's
+Holstege
+HP-UX
+icnd
+Itanium
+Jacinta
+Limbic_Region
+linux
+linux-bsd-soft
+Linuxes
+lowercase
+LXer
+mutli-threading
+MVS
+myprogram
+namespace-purity
+Netware
+non-vax-like
+non-x86
+Novell
+OpenSolaris
+OpenVMS
+OSes
+OSNews
+PalmOS
+parallelised
+param
+passé
+patsolve
+Patsolve
+patsolve-3
+Patsolve's
+PDP-10
+perl4
+perl5
+PL
+Plagger
+POSIX
+POSIX-capable
+PowerPC
+py
+README
+refactor
+Refactoring
+relicensing
+rm
+RPMs
+screenshots
+setup
+shlomi
+shlomif-desktop
+shrinkwrap
+Solaris
+Spolsky's
+s's
+startup
+sublicensing
+svn
+telaviv1
+Tendra
+themable
+theming
+Tru64
+TTY
+uppercase
+urpmi
+VM
+VxWorks
+Whatsup
+whitespace
+Wikis
+x86
+x86-64
+x86-and-DOS

File t2/philosophy/computers/web/which-wiki/update-2006-07/index.html.wml

 <p>
 <a href="http://software.newsforge.com/software/05/06/21/1641223.shtml?tid=74&amp;tid=48">An
 article on Newsforge.com covered ways to deal with wiki spam</a> back on June,
-2005. While the article was pretty good, it had a few ommissions. One of them
+2005. While the article was pretty good, it had a few omissions. One of them
 was that a wiki administrator should better watch its RSS or Atom feeds for
 any activity, so in case a wiki is spammed it would be detected immediately.
 </p>