diff options
Diffstat (limited to 'install/ui')
| -rw-r--r-- | install/ui/doc/guides.json | 4 | ||||
| -rw-r--r-- | install/ui/doc/guides/debugging_web_ui/README.md | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/install/ui/doc/guides.json b/install/ui/doc/guides.json index e85f88a3e..bbed8e8d9 100644 --- a/install/ui/doc/guides.json +++ b/install/ui/doc/guides.json @@ -23,7 +23,7 @@ { "name": "Phases", "url": "guides/phases", - "title": "Appliaciton phases", + "title": "Application phases", "description": "Introduction to application phases" }, { @@ -34,4 +34,4 @@ } ] } -]
\ No newline at end of file +] 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: |