Fix typos

linuxmint · Jan 26, 2018 · 318376b · 318376b
1 parent a909ec1
commit 318376b
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/docs/how.rst b/docs/how.rst
@@ -9,7 +9,7 @@ The first thing developers try to do is understand how to reproduce the issue.
 Always give them the relevant information:
 
 * Steps you perform to always reproduce the issue on your computer (be as precise as possible)
-* Particularities in your environment which might be relevant or different than the developers environement (your locale, your drivers, etc..)
+* Particularities in your environment which might be relevant or different than the developers environment (your locale, your drivers, etc..)
 * Any relevant error message of software output
 * Screenshots which show the issue
 * Anything that might make it easier for developers to understand and/or reproduce the issue
@@ -28,7 +28,7 @@ Explain your expectation
 
 It might sound silly, but sometimes a bug report is clear on what the software does but not on what the author expects it to do. This can lead to a misunderstanding.
 
-If possible, briefly explain why you think the software behaviour is wrong and what you would expect it to do instead.
+If possible, briefly explain why you think the software behavior is wrong and what you would expect it to do instead.
 
 Be patient and pleasant
 -----------------------

diff --git a/docs/index.rst b/docs/index.rst
@@ -5,7 +5,7 @@ Linux Mint Troubleshooting Guide
       :width: 100px
       :align: right
 
-This guide will help you troubleshoot issues on your computers, find help within the commnunity and report bugs to the development team.
+This guide will help you troubleshoot issues on your computers, find help within the comnunity and report bugs to the development team.
 
 .. toctree::
    :maxdepth: 1

diff --git a/docs/responsibility.rst b/docs/responsibility.rst
@@ -11,7 +11,7 @@ At this stage you've already established the following:
 
 The goal now is to identify **what component is responsible** for the issue and the best way to find out is to proceed by elimination.
 
-During the **reproducibility** phase you identified a series of steps to reproduce the issue. You should now try to reduce the amount of steps necessary and remove components which might play a role in the issue to idenfity which one actually does.
+During the **reproducibility** phase you identified a series of steps to reproduce the issue. You should now try to reduce the amount of steps necessary and remove components which might play a role in the issue to identify which one actually does.
 
 Here are some examples:
 

diff --git a/docs/when.rst b/docs/when.rst
@@ -1,7 +1,7 @@
 When
 ====
 
-Do not open bug reports before troubleshooting is finished. A particular project might have 2 developers, 100 open bug reports, 1,000 active users on the forums and IRC and a million users overal. You should troubleshoot the issue on your own first, and as much as you can, and then rely on other users in the community for help, before interacting with the development team.
+Do not open bug reports before troubleshooting is finished. A particular project might have 2 developers, 100 open bug reports, 1,000 active users on the forums and IRC and a million users overall. You should troubleshoot the issue on your own first, and as much as you can, and then rely on other users in the community for help, before interacting with the development team.
 
 You should report a bug when all these conditions are met: