(TXT) - Refines text for post.

Author: davidjguru

_posts/2022-03-30-drupal-tips-changing-session-lifetime-for-users.md

@@ -61,7 +61,7 @@ Since it is GC, the session value may be discarded and not compulsory. If a GC a
 This value is for the browser: This is the absolute maximum time till which a browser can keep this cookie active. A 0 value here will means immediate or when the browser will be closed.  
 
 
-| ![Cookie values for creation and expiration dats]({{ site.baseurl }}/images/davidjguru_drupal_8_9_changing_session_lifetime_for_users_2.png) |
+| ![Cookie values for creation and expiration dates]({{ site.baseurl }}/images/davidjguru_drupal_8_9_changing_session_lifetime_for_users_2.png) |
 | :-------------------------------------------------------------------------------------------------------------------:        |
 |              *Cookie values for creation and expiration dates*                                           |
 
@@ -120,7 +120,7 @@ $options['gc_maxlifetime'] = 3600;
 
 Session data & Garbage Collector & Cron
 
-The time for session was set to 1 hour (in the feature-working branch ST8-467).  But this only let available the session data for the Garbage Collector of Drupal/PHP. It means that from 1 hour the session can be opened until the Garbage Collector was executed. Who’s executing the Garbage Collector? esentially, the cron in system. 
+The time for session was set to 1 hour.  But this only let available the session data for the Garbage Collector of Drupal/PHP. It means that from 1 hour the session can be opened until the Garbage Collector was executed. Who’s executing the Garbage Collector? esentially, the cron in system. 
 
 The “Automated Cron” core module was enabled and set to 1 hours. It means that really, the inactive sessions (more than 1 hour without activity) will be deleted every 1 hour now, just when cron runs and launches the Garbage Collector. Useful Drupal contrib modules we can use for more control over the session timing and roles: