update docs now that the simulation's ending 'current time' reflects the true end of the simulation run

Author: geraintpalmer

docs/Guides/Services/processor-sharing.rst

@@ -43,14 +43,14 @@ Though it looks like service times are much longer than in a regular FIFO queue,
 
     >>> ps_time_to_process_1000 = Q.current_time
     >>> ps_time_to_process_1000
-    254.0556420...
+    254.0454918...
 
     >>> ciw.seed(0) # same seed
     >>> Q = ciw.Simulation(N) # regular FIFO queue
     >>> Q.simulate_until_max_customers(1000)
     >>> fifo_time_to_process_1000 = Q.current_time
     >>> fifo_time_to_process_1000
-    254.0556420...
+    254.0454918...
 
 In Ciw two different generalisations of processor sharing are available: limited processor sharing, and capacitated processor sharing, described below. Systems exhibiting both these behaviours simultaneously can be simulated.
 

docs/Guides/Simulation/sim_maxtime.rst

@@ -4,14 +4,14 @@
 How to Simulate For a Certain Amount of Time
 ============================================
 
-Once the simulation object has been created, it can be simulated unil a certain amount of simulation-time has passed. This is done with the :code:`simulate_until_max_time` method, which takes in the :code:`max_simulation_time` positional keyword::
+Once the simulation object has been created, it can be simulated until a certain amount of simulation-time has passed. This is done with the :code:`simulate_until_max_time` method, which takes in the :code:`max_simulation_time` positional keyword::
 
     >>> Q.simulate_until_max_time(max_simulation_time=100.0)  # doctest:+SKIP
 
 Notes
 ~~~~~
 
-Note that the simulation does not finish at exactly this time. It will finish as soon as the time of the next scheduled event is after the :code:`max_simulation_time`. The clock will reach this nect event date, but not carry out the event. E.g. consider the following system with sparce events::
+Note that the simulation will finish as soon as the time of the next scheduled event is after the :code:`max_simulation_time`. The clock will reach this nect event date, but not carry out the event. E.g. consider the following system with sparce events::
 
     >>> import ciw
     >>> N = ciw.create_network(
@@ -23,11 +23,13 @@ Note that the simulation does not finish at exactly this time. It will finish as
     >>> Q = ciw.Simulation(N)
     >>> Q.simulate_until_max_time(22.0)
 
-We will see there there have been three arrivals at dates 7, 14 and 21, but only two completed services at dates 9 and 16, with the next scheduled event at date 23::
+We will see there there have been three arrivals at dates 7, 14 and 21, but only two completed services at dates 9 and 16, Next scheduled event for the arrival node is at date 28.0, the next scheduled event for the single service node is at date 23.0, and the next scheduled event date for the exit node is set if infinity.::
 
     >>> recs = Q.get_all_records() # Completed records
     >>> [r.arrival_date for r in recs]
     [7.0, 14.0]
     >>> Q.current_time
-    23.0
+    22.0
+    >>> [nd.next_event_date for nd in Q.nodes]
+    [28.0, 23.0, inf]