Fixing a few typos

backups.rst

@@ -85,7 +85,7 @@ What is the cost to retain backups for a 30-days, 6-months, or 1 year?
 Is there a business requirement for keeping backups for a specific length of time?
 
 Are there laws for maintaining electronic records for a specific period of
-time? 
+time?
 
 
 If the organization is required to adhere to Freedom of
@@ -158,7 +158,7 @@ Security implications
 
 .. TODO:: Using backups to restore to a known "good" state after an incident just serves to put the machine in a known vulnerable state (security hole that was exploited is now back in operation)
 
-.. TODO:: can be used to restore system state that can be useful in a post mortem after an incident (say the attacker covered their tracks but backups were able to capture a rootkit before it was removed or before logs wer etampered with)
+.. TODO:: can be used to restore system state that can be useful in a post mortem after an incident (say the attacker covered their tracks but backups were able to capture a rootkit before it was removed or before logs were tampered with)
 
 Recovery basics
 ===============

databases_101.rst

@@ -63,7 +63,7 @@ To connect to a MySQL database from the CLI your command would usually take this
 
 Of these flags, ``-u`` = username, ``-p`` = password, and ``-h`` = hostname.
 You may provide the password on the command prompt: ``-ppassword`` (no space after flag!).
-We strongly advise against this, as this may leave the apssword visibile in your shell history.
+We strongly advise against this, as this may leave the password visible in your shell history.
 
 Creating databases
 ==================

glossary.rst

@@ -26,7 +26,7 @@ Glossary
 
     GUI
         Pronounced "gooey", this is an acronym for a Graphical User Interface.
-        This is distintly different from a :term:`CLI`, in that the GUI typically can contain more complex visual interactions.
+        This is distinctly different from a :term:`CLI`, in that the GUI typically can contain more complex visual interactions.
         Read more here: `Wikipedia:GUI <http://en.wikipedia.org/wiki/Graphical_user_interface>`_.
 
     MAC

inits.rst

@@ -43,7 +43,7 @@ is ``initctl(8)``'s ``show-config`` command:
     ...
 
 This snippet reveals that upstart will ``stop`` the ``avahi-daemon`` at the same
-time as dbus. Unlike many other daemons that depend on the hole filesystem, upstart
+time as dbus. Unlike many other daemons that depend on the whole filesystem, upstart
 will ``start`` ``cgroup-lite`` as soon as the ``/sys`` filesystem is mounted.
 
 Upstart is also able to "supervise" programs: that is, to restart a program

monitoring_101.rst

@@ -38,7 +38,7 @@ It supports service and host altering hierarchies via parenting, so you can redu
 It supports active and passive checks.
 It has basic scheduling for on-call periods, and supports time periods in which you can disable alerting.
 
-Since Naigos is so configurable, it can often be difficult to configure for the uninitiated.
+Since Nagios is so configurable, it can often be difficult to configure for the uninitiated.
 It can use many files for configuration, and a single syntax error will prevent the system from starting.
 Additionally, the open-source version does not natively support adding and removing hosts dynamically; the configuration needs to be modified, and the server restarted to add or remove a host.
 

outages.rst

@@ -2,7 +2,7 @@ Outages
 #######
 
 
-When outages happen (and they will) it is incredibly useful to have a point person that will handle communcations while the admin focuses on resolving the issue.
+When outages happen (and they will) it is incredibly useful to have a point person that will handle communications while the admin focuses on resolving the issue.
 A common communication forum (conference call, irc, etc) that affected users can jump in get a quick status and pass along any information is useful.
 On a larger scale you would want to have a status page that is constantly updated.
 
@@ -12,7 +12,7 @@ Once an outage takes place as an Admin you have to primary functions:
 2.  Document what caused the failure.
 
 Depending on the failure and the impact #2 may actually be more important than #1.
-Assuming you have a proper DEV / QA / PROD / DR enviroment setup you should fail over to your DR systems.  
+Assuming you have a proper DEV / QA / PROD / DR environment setup you should fail over to your DR systems.
 Then take your time investigating the PROD systems to identify root cause (and build a test so you can replicate the problem at will) and come up with a proper resolution that can be documented and isn't considered a "band-aide" fix.
 Apply the change up through DEV & QA and the then to your PROD, assuming all goes well fail back from DR and run your replicated failure test to show PROD isn't going to fail from that issue again.
 Then you are safe to make the change on your DR side.

soft_skills_201.rst

@@ -128,8 +128,8 @@ perspective. Senior management within an organization will usually understand
 risks related to financials, competition, manufacturing, etc. but they often do
 not understand IT enough to make an informed decision. Operations professionals
 are the ones with the deep technical expertise required to comprehend risks,
-threads, vulnerabilitis, and countermeasures. They use this expertise to
-express their concerns in a way suitabl for senior management. This is another
+threats, vulnerabilities, and countermeasures. They use this expertise to
+express their concerns in a way suitable for senior management. This is another
 area where the Operations professional is communicating with the organization's
 leaders to advise on appropriate actions to address IT security where it makes
 sense for the organization.

virtualization_101.rst

@@ -32,7 +32,7 @@ OpenStack based cloud offering or HP's OpenStack based cloud.
 There are a variety of companies of various sizes offering these public cloud
 services.
 These services are run in the hosting company's datacenter, and an
-administrator's access to the infrastruture is limited to launching and
+administrator's access to the infrastructure is limited to launching and
 configuring virtual machines, normally through a web-based dashboard or an API.
 
 The second type of cloud is "private clouds".