webui doc: typo fixes in guides

Reviewed-By: Petr Vobornik <pvoborni@redhat.com>
This commit is contained in:
Adam Misnyovszki authored and Petr Vobornik committed 2014-04-23 17:15:41 +02:00
1 parent 01558a77df
commit 260c5bd109
2 files changed
+3 -3

No files matched your search

+2 -2
View File
@@ -23,7 +23,7 @@
{
"name": "Phases",
"url": "guides/phases",
"title": "Appliaciton phases",
"title": "Application phases",
"description": "Introduction to application phases"
},
{
@@ -34,4 +34,4 @@
}
]
}
]
]
@@ -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: