A few wording/spelling adjustments

Change-Id: Id77c7983d7d03319ffcb945268cb972ae53552b6

taskflow/examples/fake_boot_vm.py

@@ -84,10 +84,11 @@ class ValidateAPIInputs(task.Task):
 
 # Simulates reserving the space for a vm and associating the vm to be with
 # a unique identifier.
-class PeformReservation(task.Task):
+class PerformReservation(task.Task):
     def __init__(self):
-        super(PeformReservation, self).__init__('reserve-vm',
-                                                provides='vm_reservation_spec')
+        super(PerformReservation, self).__init__('reserve-vm',
+                                                 provides='vm_reservation_'
+                                                          'spec')
 
     def revert(self, context, vm_spec, result):
         reserved_spec = result
@@ -157,7 +158,7 @@ class BootVM(task.Task):
 # Lets try booting a vm (not really) and see how the reversions work.
 flow = gf.Flow("Boot-Fake-Vm").add(
     ValidateAPIInputs(),
-    PeformReservation(),
+    PerformReservation(),
     ScheduleVM(),
     BootVM())
 

taskflow/states.py

@@ -81,7 +81,7 @@ _ALLOWED_FLOW_TRANSITIONS = frozenset((
 
 
 # NOTE(imelnikov) SUCCESS->RUNNING and FAILURE->RUNNING transitions are
-# useful when flow or flowdetails baciking it were altered after the flow
+# useful when flow or flowdetails backing it were altered after the flow
 # was finished; then, client code may want to run through flow again
 # to ensure all tasks from updated flow had a chance to run.
 
@@ -109,7 +109,7 @@ def check_flow_transition(old_state, new_state):
 
     If transition can be performed, it returns True. If transition
     should be ignored, it returns False. If transition is not
-    invalid, it raises InvalidStateException.
+    valid, it raises InvalidStateException.
     """
     if old_state == new_state:
         return False