Fix typos in Swift files

Change-Id: I34e0c9a888127704ac1910e73ddd14e27ebade13

bin/swift-init

@@ -77,7 +77,7 @@ def main():
     # SIGKILL daemon after kill_wait period
     parser.add_option('--kill-after-timeout', dest='kill_after_timeout',
                       action='store_true',
-                      help="Kill daemon and all childs after kill-wait "
+                      help="Kill daemon and all children after kill-wait "
                            "period.")
 
     options, args = parser.parse_args()

bin/swift-reconciler-enqueue

@@ -25,7 +25,7 @@ from swift.container.reconciler import add_to_reconciler_queue
 """
 This tool is primarily for debugging and development but can be used an example
 of how an operator could enqueue objects manually if a problem is discovered -
-might be particularlly useful if you need to hack a fix into the reconciler
+might be particularly useful if you need to hack a fix into the reconciler
 and re-run it.
 """
 

doc/manpages/swift-object-expirer.1

@@ -63,7 +63,7 @@ The options are as follows:
 .LP
 More in depth documentation in regards to
 .BI swift-object-expirer
-can be foud at 
+can be found at
 .BI http://swift.openstack.org/overview_expiring_objects.html
 and also about Openstack-Swift as a whole can be found at
 .BI http://swift.openstack.org/index.html

doc/source/ops_runbook/diagnose.rst

@@ -575,7 +575,7 @@ command-line wrong.
 Pick a ``source`` and ``target`` node. The source is often a proxy node
 and the target is often an object node. Using the same source proxy you
 can test communication to different object nodes in different AZs to
-identity possible bottlekecks.
+identity possible bottlenecks.
 
 Running tests
 ^^^^^^^^^^^^^