update docs LogFileSize

Signed-off-by: Naren Krishna <naren@ponder.io>

docs/usage_guide/advanced_usage/modin_logging.rst

@@ -8,8 +8,10 @@ in addition to Modin API calls (see the usage examples below).
 
 The logs generated by Modin Logging will be written to a ``.modin/logs/job_<uuid>`` directory, uniquely named after the job uuid.
 The logs that contain the Modin API stack traces are named ``trace.log``. The logs that contain the memory utilization metrics are
-named ``memory.log``. By default, if any log file exceeds 10MB, the logs will rollover and several files will be created. For instance, if
-users have 20MB worth of Modin API logs, they can expect to find ``trace.log.1`` and ``trace.log.2`` in the ``.modin/logs/job_<uuid>`` directory.
+named ``memory.log``. By default, if any log file exceeds 10MB (configurable with ``LogFileSize``), that file will be saved and a 
+separate log file will be created. For instance, if users have 20MB worth of Modin API logs, they can expect to find ``trace.log.1`` 
+and ``trace.log.2`` in the ``.modin/logs/job_<uuid>`` directory. After ``10 * LogFileSize`` MB or by default 100MB of logs, the logs will 
+rollover and the original log files beginning with ``trace.log.1`` will be overwritten with the new log lines.
 
 **Developer Warning:** In some cases, running services like JupyterLab in the ``modin/modin`` directory may result in circular dependency issues.
 This is due to a naming conflict between the ``modin/logging`` directory and the Python ``logging`` module, which may be used as a default in