Minor updates.

diff --git a/blog/data/2009-02-18-protokoll-og-format.txt b/blog/data/2009-02-18-protokoll-og-format.txt
index 4d8ff96ba8f0ea88d93ab777c5cec5faf2cf8429..8601d58d3292f7bccf460625f92fd045bc3b433f 100644 (file)
--- a/blog/data/2009-02-18-protokoll-og-format.txt
+++ b/blog/data/2009-02-18-protokoll-og-format.txt
@@ -6,7 +6,7 @@ Publish: 2009-03-30
 <p>Where I work at the University of Oslo, one decision stand out as a
 very good one to form a long lived computer infrastructure.  It is the
 simple one, lost by many in todays computer industry: Standardize on
 <p>Where I work at the University of Oslo, one decision stand out as a
 very good one to form a long lived computer infrastructure.  It is the
 simple one, lost by many in todays computer industry: Standardize on

-open network protocols and exchange/storage formats, not applications.
+open network protocols and open exchange/storage formats, not applications.

 Applications come and go, while protocols and files tend to stay, and
 thus one want to make it easy to change application and vendor, while
 avoiding conversion costs and locking users to a specific platform or
 Applications come and go, while protocols and files tend to stay, and
 thus one want to make it easy to change application and vendor, while
 avoiding conversion costs and locking users to a specific platform or


@@ -22,7 +22,7 @@ blocked from doing so.</p>
 
 <p>It also allow us to replace the server side without forcing the
 users to replace their applications, and thus allow us to select the
 
 <p>It also allow us to replace the server side without forcing the
 users to replace their applications, and thus allow us to select the

-best server implementation over time, when scale and resouce
+best server implementation at any moment, when scale and resouce

 requirements change.</p>
 
 <p>I strongly recommend standardizing - on open network protocols and
 requirements change.</p>
 
 <p>I strongly recommend standardizing - on open network protocols and