[Gzz-commits] manuscripts/UMLLink article.rst

[Tuukka Hastrup]

CVSROOT:        /cvsroot/gzz
Module name:    manuscripts
Changes by:     Tuukka Hastrup <address@hidden> 03/02/15 13:08:51

Modified files:
        UMLLink        : article.rst 

Log message:
        small changes in intro

CVSWeb URLs:
http://savannah.gnu.org/cgi-bin/viewcvs/gzz/manuscripts/UMLLink/article.rst.diff?tr1=1.73&tr2=1.74&r1=text&r2=text

Patches:
Index: manuscripts/UMLLink/article.rst
diff -u manuscripts/UMLLink/article.rst:1.73 
manuscripts/UMLLink/article.rst:1.74
--- manuscripts/UMLLink/article.rst:1.73        Sat Feb 15 13:05:43 2003
+++ manuscripts/UMLLink/article.rst     Sat Feb 15 13:08:51 2003
@@ -9,7 +9,7 @@
 .. Alternative title: "Free Software toolchain for bidirectional 
    linking between UML diagrams and Javadoc"
 
-.. :Stamp: $Id: article.rst,v 1.73 2003/02/15 18:05:43 tuukkah Exp $
+.. :Stamp: $Id: article.rst,v 1.74 2003/02/15 18:08:51 tuukkah Exp $
 
 .. Points for HT people
    ====================
@@ -78,6 +78,7 @@
    * web
    * user interfaces
    * spatial menus
+   * navigational maps
 
 Abstract
 ========
@@ -106,10 +107,10 @@
 Software projects manage a large base of evolving documentation, which
 is inter-related on many levels. Design documentation gives
 architectural views on a more general level, while the program code
-source files contain interfaces and often embedded documentation
-giving details on how the interfaces should be used. Although
+source files contain minute interface specifications and often also embedded 
+documentation giving details on how the interfaces should be used. Although
 these two parts of documentation are semantically dependent, linking
-them by hand is tedious and error-prone since they are authored using different
+them by hand is tedious and error-prone when they are authored using different
 software. 
 
 In this article, we present a navigational aid for software engineering 
documentation.