From 442de9b239c6feb60a3c95bce8e7762a4cf52047 Mon Sep 17 00:00:00 2001
From: mh17 <mh17>
Date: Tue, 1 Jun 2010 09:26:52 +0000
Subject: [PATCH] version number

---
 doc/Design_notes/index.html          | 2 +-
 doc/Design_notes/notes/optimise.html | 4 +++-
 2 files changed, 4 insertions(+), 2 deletions(-)

diff --git a/doc/Design_notes/index.html b/doc/Design_notes/index.html
index d118d1388..f7727a398 100644
--- a/doc/Design_notes/index.html
+++ b/doc/Design_notes/index.html
@@ -1,4 +1,4 @@
-<!-- $Id: -->
+<!-- $Id: index.html,v 1.14 2010-06-01 09:26:52 mh17 Exp $ -->
 
 <h2>ZMap Design Documentation</h2>
 
diff --git a/doc/Design_notes/notes/optimise.html b/doc/Design_notes/notes/optimise.html
index eb8a39111..f286ba658 100644
--- a/doc/Design_notes/notes/optimise.html
+++ b/doc/Design_notes/notes/optimise.html
@@ -1,8 +1,10 @@
+<!-- $Id: optimise.html,v 1.2 2010-06-01 09:27:17 mh17 Exp $ -->
+
 <h2>Optimising ZMap</h2>
 
 <fieldset><legend>Overview</legend>
 <p>
-Some ZMap functions take a long time, notably 3-Frame toggle and RevComp, zoom andwe wish to make these run much faster.  The design so far has been to display all the data so that it is displayed in a single bitmap which can be scrolled using hardware and inevitably as data size increases display functions get slower.
+Some ZMap functions take a long time, notably 3-Frame toggle and RevComp, zoom and we wish to make these run much faster.  The design so far has been to display all the data so that it is displayed in a single bitmap which can be scrolled using hardware and inevitably as data size increases display functions get slower.
 </p>
 
 <p>
-- 
GitLab