summaryrefslogtreecommitdiffstats
path: root/install/ui/doc/guides/debugging_web_ui/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'install/ui/doc/guides/debugging_web_ui/README.md')
-rw-r--r--install/ui/doc/guides/debugging_web_ui/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/install/ui/doc/guides/debugging_web_ui/README.md b/install/ui/doc/guides/debugging_web_ui/README.md
index bac3c30a6..1bf9bd9a2 100644
--- a/install/ui/doc/guides/debugging_web_ui/README.md
+++ b/install/ui/doc/guides/debugging_web_ui/README.md
@@ -67,7 +67,7 @@ Notes:
## Conclusion
-While reporting an UI bug it's good the check if there is some JavaScript error and if so send a call stack with line numbers, preferably the ones by using source codes. If source codes are not available, pretty print function should be used and send also code (~15 lines on both sides) around the bug.
+While reporting an UI bug it's good to check if there is some JavaScript error and if so, send a call stack with line numbers, preferably the ones by using source codes. If source codes are not available, pretty print function should be used and send also code (~15 lines on both sides) around the bug.
The most valuable information in order of preference are: