diff --git a/Issue-Guidelines.md b/Issue-Guidelines.md
index 8679d48..294ffbb 100644
--- a/Issue-Guidelines.md
+++ b/Issue-Guidelines.md
@@ -23,8 +23,8 @@ If your issue is not clear or does not meet the guidelines, then it will be clos
 1. **Clear Title:** Add a clear subject to your bug report like "Unable to submit Purchase Order without Basic Rate" instead of just "Cannot Submit"
 1. **Version Number:** Please add version numbers of Frappe and ERPNext in your report. Often a bug is fixed in the latest version. It's usually helpful to provide version number of your browser as well.
 1. **Steps to Reproduce:** The bug report must have a list of steps needed to reproduce a bug. If we cannot reproduce it, then we cannot solve it.
-1. **Actual behavior** After describing steps to reproduce, please explain what exactly fails or behaves wrong, according to your opinion.
-1. **Expected behavior** Describe what and how should be done in a proper way.
+1. **Actual behavior:** After describing steps to reproduce, please explain what exactly fails or behaves wrong, according to your opinion.
+1. **Expected behavior:** Describe what and how should be done in a proper way.
 1. **Screenshots:** Screenshots are a great way of communicating the issues. Try adding annotations or using LiceCAP to take a screencast in `gif`.
 
 ### Feature Request Guidelines