[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/21 04:25:50

Modified files:
        UMLLink        : short-paper.rst 

Log message:
        twids

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

Patches:
Index: manuscripts/UMLLink/short-paper.rst
diff -u manuscripts/UMLLink/short-paper.rst:1.17 
manuscripts/UMLLink/short-paper.rst:1.18
--- manuscripts/UMLLink/short-paper.rst:1.17    Wed May 21 02:47:20 2003
+++ manuscripts/UMLLink/short-paper.rst Wed May 21 04:25:49 2003
@@ -2,7 +2,7 @@
 Bridging Javadoc and design documentation via UML diagram image maps
 ====================================================================
 
-.. $Id: short-paper.rst,v 1.17 2003/05/21 06:47:20 tjl Exp $
+.. $Id: short-paper.rst,v 1.18 2003/05/21 08:25:49 tjl Exp $
 
 .. short paper == 2 pages, deadline the end of May
 
@@ -98,7 +98,8 @@
 are and how one creates them. 
 These diagrams certainly exist for all properly managed 
 medium-to-large scale software projects --- the problem is getting
-them to where it matters.
+them to where it matters without having to manually insert
+links into the low-level documentation.
 
 .. at ``http://java.sun.com/j2se/1.4.1/docs/api/java/security/PublicKey.html``.
 
@@ -166,7 +167,7 @@
 team. Each UML diagram is meant to expose a particular aspect
 of the design. 
 Therefore
-a single program element may appear on several distinct diagrams, 
+a single program element often appears on several distinct diagrams, 
 that 
 together create a multicontext view for the element.