From ec10fd80375fa193de728c465d415a1d704c7cdc Mon Sep 17 00:00:00 2001 From: Naren Krishna <92325366+naren-ponder@users.noreply.github.com> Date: Tue, 7 Jun 2022 12:14:03 -0700 Subject: [PATCH] Update docs/usage_guide/advanced_usage/modin_logging.rst Co-authored-by: Yaroslav Igoshev --- docs/usage_guide/advanced_usage/modin_logging.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/usage_guide/advanced_usage/modin_logging.rst b/docs/usage_guide/advanced_usage/modin_logging.rst index 3ccbfce24a1..a30d4192c6f 100644 --- a/docs/usage_guide/advanced_usage/modin_logging.rst +++ b/docs/usage_guide/advanced_usage/modin_logging.rst @@ -13,7 +13,7 @@ users have 20MB worth of Modin API logs, you can expect to find `trace.log.1` an **Developer Warning:** In some cases, running services like JupyterLab in the `modin/modin` directory may result in circular dependency issues. This is as a result of a name conflict between the `modin/logging` directory and the Python `logging` module, which may be used as a default in -such environments. As a resolution, one one could run Jupyterlab or other services from any directory except `modin/modin`. +such environments. As a resolution, one could run Jupyterlab or other services from any directory except `modin/modin`. Usage examples --------------