From a96ba536f87622273808307b6b3b4455ad5a760d Mon Sep 17 00:00:00 2001 From: Chinzorig Ochirbat <78355406+Chinzorig11@users.noreply.github.com> Date: Wed, 6 May 2026 10:24:07 +0800 Subject: [PATCH] Fix typos in DEVELOPMENT_GUIDE.md --- DEVELOPMENT_GUIDE.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/DEVELOPMENT_GUIDE.md b/DEVELOPMENT_GUIDE.md index 5d2cf5831..6e1a128cc 100644 --- a/DEVELOPMENT_GUIDE.md +++ b/DEVELOPMENT_GUIDE.md @@ -71,7 +71,7 @@ Since black is installed in virtualenv, when you follow [this instruction](https /Users//.pyenv/shims/black ``` -However, IDEs such PyChaim (using FileWatcher) will have a hard time invoking `/Users//.pyenv/shims/black` +However, IDEs such as PyCharm (using FileWatcher) will have a hard time invoking `/Users//.pyenv/shims/black` and this will happen: ``` @@ -185,7 +185,7 @@ conventions are best practices that we have learnt over time. are raised by Python interpreter and usually signify a bug in your code. Your method must not explicitly raise these exceptions because the caller has no way of knowing whether it came from a bug or not. - Custom exceptions convey are must better at conveying the intent and + Custom exceptions convey intent much better and can be handled appropriately by the caller. In HTTP lingo, custom exceptions are equivalent to 4xx (user\'s fault) and built-in exceptions are equivalent to 5xx (Service Fault)