found good definition of transitive

diff --git a/updates/018_2019may27_nlnet_grant_approved.mdwn b/updates/018_2019may27_nlnet_grant_approved.mdwn
index b15ae18c1d8165a8fc4062783e6a127af27924e0..2acf847971cf8cbd7bf12a760a916d189e56130f 100644 (file)
--- a/updates/018_2019may27_nlnet_grant_approved.mdwn
+++ b/updates/018_2019may27_nlnet_grant_approved.mdwn
@@ -108,7 +108,7 @@ family that AMD had to publish "Intel equivalent" speed numbers for,
 because it was so much more efficient and effective than Intel's designs)
 each instruction "accumulated" the dependencies of all prior instructions
 being issued in the same batch.  This works because read and write
 because it was so much more efficient and effective than Intel's designs)
 each instruction "accumulated" the dependencies of all prior instructions
 being issued in the same batch.  This works because read and write

-dependencies are *transitive* (Google it...)
+dependencies are *transitive* (whenever a -> b and b -> c then a -> c).

 
 What that means, in practical terms, is that we have a way to create a
 design that could, if ramped up, take on the big boys.  To make that
 
 What that means, in practical terms, is that we have a way to create a
 design that could, if ramped up, take on the big boys.  To make that