Clean up trailing and leading whitespace

app/views/layouts/tutorial/injection/_injection_command.html.erb

@@ -37,7 +37,7 @@
 			  </p>
 			  <p>
 				Within app/controllers/benefits_controller.rb:
-			  </p>		
+			  </p>
 			  <pre class="ruby">
 				  def upload
 				    <span style="background:yellow">file = params[:benefits][:upload]</span>
@@ -46,7 +46,7 @@
 				      <span style="background:yellow">Benefits.save(file, params[:benefits][:backup])</span>
 				    else
 				      flash[:error] = "Something went wrong"
-				    end   
+				    end
 				    redirect_to user_benefit_forms_path(:user_id => current_user.user_id)
 				  end
 			  </pre>
@@ -71,11 +71,11 @@
 				 end
 
 				end
-				
-			  </pre>	
+
+			  </pre>
 			  <p class="desc">
 				The command injection vulnerability is introduced when the user-supplied input (name of file) is interpolated or mixed in with a system command.
-			  </p>	
+			  </p>
             </div>
           </div>
         </div>
@@ -92,7 +92,7 @@
                <p><b>Command Injection - ATTACK</b></p>
 			   <p class="desc">
 			   	The filename portion of the benefits[upload] parameter is vulnerable to command injection. Navigate to the benefits section of the application, and choose a file to upload. Once the file is chosen, turn your intercepting proxy on, click start upload, and intercept the request. you will want to change the backup option to true (highlighted below) and inject your commands within the filename parameter (highlighted). Note: forward slashes ('/') are escaped by the original_filename method (used to extract the file name ).
-			   </p>	
+			   </p>
  			   <pre class='ruby'>
 				POST /upload HTTP/1.1
 				Host: railsgoat.dev
@@ -124,16 +124,16 @@
 			   </pre>
 			   <p><b>Command Injection - SOLUTION</b></p>
 			   <p class="desc">
-				The solution is fairly simple and because this is so poorly done there are numerous ways to fix the vulnerability. One option, is to abstract a file creation method and pass it options such as the path and filename, then call it twice, once for the initial upload and another for the backup. Another option is to make a copy through the use of the FileUtils. 
+				The solution is fairly simple and because this is so poorly done there are numerous ways to fix the vulnerability. One option, is to abstract a file creation method and pass it options such as the path and filename, then call it twice, once for the initial upload and another for the backup. Another option is to make a copy through the use of the FileUtils.
 			   </p>
 			   <p>
 				As an example:
-			   </p>	
-			   <pre class="ruby"> 
+			   </p>
+			   <pre class="ruby">
 					def self.make_backup(file, data_path, full_file_name)
 					   FileUtils.cp "#{full_file_name}", "#{data_path}/bak#{Time.now.to_i}_#{file.original_filename}"
 					 end
-			   </pre>	
+			   </pre>
             </div>
           </div>
         </div>
@@ -150,7 +150,7 @@
               Let's create a backup when uploading a file, wonder how they are naming it?
             </div>
           </div>
-        </div> 
+        </div>
 	 </div>
     </div>
   </div>