bootcount: clarify documentation

- Grammar fixes
- Clarify explanations

Signed-off-by: Michael Opdenacker <michael.opdenacker@bootlin.com>
Reviewed-by: Heiko Schocher <hs@denx.de>
diff --git a/drivers/bootcount/Kconfig b/drivers/bootcount/Kconfig
index 607027c..65c052f 100644
--- a/drivers/bootcount/Kconfig
+++ b/drivers/bootcount/Kconfig
@@ -68,15 +68,15 @@
 	  "bootcount" is stored in the environment. To prevent a
 	  saveenv on all reboots, the environment variable
 	  "upgrade_available" is used. If "upgrade_available" is
-	  0, "bootcount" is always 0, if "upgrade_available" is
-	  1 "bootcount" is incremented in the environment.
+	  0, "bootcount" is always 0. If "upgrade_available" is 1,
+          "bootcount" is incremented in the environment.
 	  So the Userspace Application must set the "upgrade_available"
-	  and "bootcount" variable to 0, if a boot was successfully.
+	  and "bootcount" variables to 0, if the system booted successfully.
 
 config BOOTCOUNT_RAM
 	bool "Boot counter in RAM"
 	help
-	  Store the bootcount in DRAM protected against against bit errors
+	  Store the bootcount in DRAM protected against bit errors
 	  due to short power loss or holding a system in RESET.
 
 config BOOTCOUNT_I2C
@@ -166,7 +166,7 @@
 	help
 	  Set the Maximum number of reboot cycles allowed without the boot
 	  counter being cleared.
-	  If set to 0 do not set a boot limit in the environment.
+	  If set to 0, do not set a boot limit in the environment.
 
 config BOOTCOUNT_ALEN
 	int "I2C address length"