Update bug_report.md

.github/ISSUE_TEMPLATE/bug_report.md

@@ -13,22 +13,18 @@ A clear and concise description of what the bug is.
 
 ## To Reproduce
 
-Steps to reproduce the behavior:
-1. Go to '...'
-2. Click on '....'
-3. Perform '....'
-4. See error
+Provide the steps to reproduce the behavior.
 
 ## Expected behavior
 
 A clear and concise description of what you expected to happen.
 
-## Log or Support bundle
+## Support bundle for troubleshooting
 
-If applicable, add the Longhorn managers' log or support bundle when the issue happens. 
-You can generate a Support Bundle using the link at the footer of the Longhorn UI.
+Provide a support bundle when the issue happens. You can generate a support bundle using the link at the footer of the Longhorn UI. Check [here](https://longhorn.io/docs/latest/advanced-resources/support-bundle/).
 
 ## Environment
+> Suggest checking the doc of the best practices of using Longhorn. [here](https://longhorn.io/docs/1.5.1/best-practices/#minimum-recommended-hardware)
 
  - Longhorn version:
  - Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
@@ -39,7 +35,7 @@ You can generate a Support Bundle using the link at the footer of the Longhorn U
    - OS type and version:
    - CPU per node:
    - Memory per node:
-   - Disk type(e.g. SSD/NVMe):
+   - Disk type(e.g. SSD/NVMe/HDD):
    - Network bandwidth between the nodes:
  - Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
  - Number of Longhorn volumes in the cluster: