[Commits] [svn:einsteintoolkit] Paper_EinsteinToolkit_2010/ (Rev. 199)

[knarf at cct.lsu.edu]

User: knarf
Date: 2011/11/14 12:30 AM

Modified:
 /
  ET.tex

Log:
 cosmetics in design

File Changes:

Directory: /
============

File [modified]: ET.tex
Delta lines: +4 -4
===================================================================
--- ET.tex	2011-11-14 06:28:18 UTC (rev 198)
+++ ET.tex	2011-11-14 06:30:24 UTC (rev 199)
@@ -332,15 +332,15 @@
 ({\tt trac.einsteintoolkit.org}), with submissions also open to the public.
 
 Despite this open design, some actions naturally have to be restricted to a smaller
-group of maintainers. This is true for, e.g., administrative tasks like the
+group of maintainers. This is true for administrative tasks like the
 setup and maintenance of the services themselves, or to avoid large amounts
 of spam. One of the most important tasks of an Einstein Toolkit
 maintainer is to review and apply patches sent by users in order to ensure
 a high software quality level. Every substantial change or addition to
-the toolkit has to be reviewed by another Einstein Toolkit maintainer,
+the toolkit must be reviewed by another Einstein Toolkit maintainer,
 and is generally open for discussion on the users mailing list. This convention,
-despite not being technically enforced, works well in practice, and is at the
-same time promoting active development.
+though not being technically enforced, works well in practice and promotes
+active development.
 
 \section{Core Technologies}