summaryrefslogtreecommitdiffstats
path: root/install
diff options
context:
space:
mode:
authorAdam Misnyovszki <amisnyov@redhat.com>2014-04-11 19:31:19 +0200
committerPetr Vobornik <pvoborni@redhat.com>2014-04-23 17:15:41 +0200
commit260c5bd10927d3e01202ed1cccbdf4463c98e8a5 (patch)
treecef7a77116c7774c50db6de6877b7fcd9f237c6e /install
parent01558a77df9881de5e5c6919b373c77f2780ecde (diff)
downloadfreeipa-260c5bd10927d3e01202ed1cccbdf4463c98e8a5.tar.gz
freeipa-260c5bd10927d3e01202ed1cccbdf4463c98e8a5.tar.xz
freeipa-260c5bd10927d3e01202ed1cccbdf4463c98e8a5.zip
webui doc: typo fixes in guides
Reviewed-By: Petr Vobornik <pvoborni@redhat.com>
Diffstat (limited to 'install')
-rw-r--r--install/ui/doc/guides.json4
-rw-r--r--install/ui/doc/guides/debugging_web_ui/README.md2
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: