Fix documentation

README.md

@@ -53,15 +53,15 @@ What should be said is that since the `search_length` window is continuously mov
 
 ### Static
 
-> **NOT FINISHED**: This version of planner is still not fully functional, need some more work to work properly. For now the planner does not guarantee that the `duration` amount of hours are found inside the search-window.
+> **NOT FINISHED**: This version of planner is still not fully functional, need some more work to work properly. For now the planner will search for the remaining duration (duration - spent-hours) in the remaining time-span. This means that as you close in to fulfilling the `duration` it will get smaller and it could be that the active time is aborted for a while since there is easier to find cheaper average further ahead. Normally this should not happen as the price-curve in most cases has a concave shape and once you have found the initial best match for cheap hours it includes both the falling and rising edge of curve (will only get more expensive closer to the `end_hour`)
 
-Two non-optional configuration entities will be created and you need to set these to a value that matches your consumption profile.
+Three non-optional configuration entities will be created and you need to set these to a value that matches your consumption profile.
 
 * `start_hour` specifies the time of day the searching shall start.
 * `end_hour` specifies the time of day the searching shall stop.
 * `duration` For now this entity specified how many hours of low-price shall be found inside the search range.
 
-More to come about the expected behavior once it's finished.
+More to come about the expected behavior once it fully implemented.
 
 ## Optional features