Provide feature update

README.md

@@ -1,6 +1,6 @@
-# Update Nov 26th 2021: Completion prediction - a new feature!
+# Update Dec 3rd 2021: Date Reinforcment - Win earlier completion dates!
 
-I had to have some way of knowing when I will complete the study of a course using GlideCLI. So I made this feature that will tell me!
+I thought it would be more reinforcing to see how many repetitions I need to complete the predicted date. Then I thought it would be cool to see if I could win an earlier completion date! 
 
 
 # About
@@ -12,6 +12,7 @@ Glide allows people who use it to study more efficiently, and learn at a very fa
 * exit from menu
 * Change number of total questions on first study of a topic
 * Predicts the date a course will be completed by.
+* UAllows users to win earlier completion dates.
 
 # To Install:
 GlideCLI MIGHT run on MacOS now. It WILL now run on Windows, Linux, and Docker:
@@ -46,3 +47,4 @@ The calculation is inaccurate, because it can produce a result below the value o
 
 I had to invent a way to calculate difficulty, because I could not find that research document on the Easiness Factor, until after I had written this program. I knew that the calculation of difficulty had to be constrained between these values inclusively, (1.3, and 2.5), and the image of a sloped line on a graph, intersecting y at 1.3, and x at 0, just popped into my head. So I applied the point slope formula to calculate difficulty, and it works perfect. So perfect, that difficulty does not need to be re-calculated for every repetition. It only needs to be calculated on the first repetition. If you look at the pdf file that I linked in the about section (https://github.com/Dartomic/GlideCLI/blob/master/Docs/Manual.pdf), I go into great detail to explain how difficulty is calculated there. Although, it is very simple. I just wanted to be as detailed as I could be so that it is understood how it is more accurate than the research article's version.
 
+