From b5795b8c827d8036eda9cc18a490f4356f8832be Mon Sep 17 00:00:00 2001
From: Petter Reinholdtsen <pere@hungry.com>
Date: Thu, 24 Sep 2015 13:19:59 +0200
Subject: [PATCH] A bit more text.

---
 blog/data/2015-09-24-laptop-battery.txt | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/blog/data/2015-09-24-laptop-battery.txt b/blog/data/2015-09-24-laptop-battery.txt
index 638b0350b3..f2c7be3522 100644
--- a/blog/data/2015-09-24-laptop-battery.txt
+++ b/blog/data/2015-09-24-laptop-battery.txt
@@ -31,7 +31,7 @@ battery stats ever since. Now my
 /var/log/hjemmenett-battery-status.log file contain around 115,000
 measurements, from the time the battery was working great until now,
 when it is unable to charge above 7% of original capasity.  My
-colletor shell script look like this:</p>
+colletor shell script is quite simple and look like this:</p>
 
 <pre>
 #!/bin/sh
@@ -112,3 +112,12 @@ Linux too.</p>
 <p>Is there a way with Linux to tell the battery to stop charging at
 80%, unless requested to charge to 100% once in preparation for a
 longer trip?</p>
+
+<p>I wonder why the battery capacity was reported to be more than 100%
+at the start.  I also wonder why the "full capacity" increases some
+times, and if it is possible to repeat the process to get the battery
+back to design capacity.  And I wonder if the discharge and charge
+speed change over time, or if this stay the same.  I did not yet try
+to write a tool to calculate the derivative values of the battery
+level, but suspect some interesting insights might be learned from
+those.</p>
-- 
2.47.2