From db1c2db7d844afc40edcc6ea27f4e4100a0dd30d Mon Sep 17 00:00:00 2001 From: Tryking Date: Sun, 29 Sep 2019 16:21:01 +0800 Subject: [PATCH] correct spelling (#882) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f0134b958..6340cbf7b 100644 --- a/README.md +++ b/README.md @@ -19,7 +19,7 @@ Arthas allows developers to troubleshoot production issues for Java applications Often times, the production system network is inaccessible from the local development environment. If issues are encountered in production systems, it is impossible to use IDEs to debug the application remotely. More importantly, debugging in production environment is unacceptable, as it will suspend all the threads, resulting in the suspension of business services. -Developers could always try to reproduce the same issue on the test/staging environment. However, this is tricky as some issues cannot be be reproduced easily on a different environment, or even disappear once restarted. +Developers could always try to reproduce the same issue on the test/staging environment. However, this is tricky as some issues cannot be reproduced easily on a different environment, or even disappear once restarted. And if you're thinking of adding some logs to your code to help troubleshoot the issue, you will have to go through the following lifecycle; test, staging, and then to production. Time is money! This approach is inefficient! Besides, the issue may not be reproducible once the JVM is restarted, as described above.