README.md in action_logic-0.1.0 vs README.md in action_logic-0.2.0

@@ -481,23 +481,23 @@
 to expirement and play with the flexibility provided to you by `ActionContext` in determining what is optimal for your given code contexts and your team.
 
 ```ruby
 class RailsControllerExample < ApplicationController
   def create
-		case create_use_case.status
-		when :disposition_1 then ActionUseCaseSuccess1.execute(create_use_case)
-		when :disposition_2 then ActionUseCaseSuccess2.execute(create_use_case)
-		when :disposition_9 then ActionUseCaseFailure.execute(create_use_case)
-		else
-		  ActionUseCaseDefault.execute(create_use_case)
-		end
-	end
+    case create_use_case.status
+      when :disposition_1 then ActionUseCaseSuccess1.execute(create_use_case)
+      when :disposition_2 then ActionUseCaseSuccess2.execute(create_use_case)
+      when :disposition_9 then ActionUseCaseFailure.execute(create_use_case)
+      else
+        ActionUseCaseDefault.execute(create_use_case)
+    end
+  end
 
-	private
+  private
 
-	def create_use_case
-	  @create_use_case ||= ActionUseCaseExample.execute(params)
-	end
+  def create_use_case
+    @create_use_case ||= ActionUseCaseExample.execute(params)
+  end
 end
 ```
 
 Although this contrived example would be ideal for an `ActionCoordinator` (because the result of `ActionUseCaseExample` drives the execution of the next `ActionUseCase`), this
 example serves to show that `status` can be used with custom disposition codes to drive branching behavior.