Implementation.md

@@ -29,10 +29,9 @@ See [the related doc](Functions#input) for details on the technical implementati
 
 At the beginning of each cycle, the simulator asks for input, which is at the core of the human-machine interface. In the long run, this could be used, for instance, as the result of mouse movement, controller input, keyboard presses, sensors, microphone, whatever you want that can be transmitted as a digital signal basically. 
 
-Currently, however, such, let's admit it, cool features, are out of question since the input's main function is to deprive the user of sleep by giving a new prompt for each bit on `stdin`. Of course, the user can still copy-paste its way through it, or make a script which pipes the input in, but that's not very user-friendly.
+Currently, however, such, let's admit it, cool features, are out of question since the input is necessarily `stdin`. Of course, the user can still make a script which pipes the input in, but that's not very user-friendly.
 
 ## TODO
-- Change this damned input method to take bit-words as input for buses.
 - Have a way to choose where the input comes from (file, user actions...)
 
 # Computations