[Gzz-commits] manuscripts/UMLLink short-paper.rst

[Tuomas J. Lukka]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuomas J. Lukka <address@hidden>        03/05/29 12:44:46

Modified files:
        UMLLink        : short-paper.rst 

Log message:
        twids--fits

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/short-paper.rst.diff?tr1=1.46&tr2=1.47&r1=text&r2=text

Patches:
Index: manuscripts/UMLLink/short-paper.rst
diff -u manuscripts/UMLLink/short-paper.rst:1.46 
manuscripts/UMLLink/short-paper.rst:1.47
--- manuscripts/UMLLink/short-paper.rst:1.46    Thu May 29 12:00:36 2003
+++ manuscripts/UMLLink/short-paper.rst Thu May 29 12:44:46 2003
@@ -44,8 +44,8 @@
 
     \begin{abstract}
     We present a navigational aid for documentation used in software
-    development. Based on using readily-authored UML diagrams as
-    multi-ended links, we hypertexturally connect two distinct areas
+    development. Based on using human-made UML diagrams as
+    multi-ended links, we hypertextually connect two distinct areas
     of documentation: design documents and 
     documentation embedded in the program code, such as Javadoc. 
     \end{abstract}
@@ -60,12 +60,11 @@
 
 Software projects manage a large base of evolving documentation, whose
 parts are
-inter-related on many levels. 
+interrelated on many levels. 
 Design documentation shows
 architectural views on a more general level, while 
-the source code (in e.g. Java and nowadays often also C++)
-contains
-embedded documentation giving details on the concrete
+the source code usually contains
+embedded documentation such as Javadoc [friendly95javadoc]_ giving details on 
the concrete
 classes and methods.
 
 .. Since these parts of documentation are semantically dependent