+
+1. Clone our [ruby testing repo](https://github.com/TheOdinProject/ruby_testing) and complete the lessons in the spec folder.
+1. Go back to the [Caesar Cipher Project](/lessons/ruby-caesar-cipher) and write tests for your code. It shouldn't take more than a half-dozen tests to cover all the possible cases. As always, use the git workflow you learned in [Revisiting Rock Paper Scissors](https://www.theodinproject.com/lessons/foundations-revisiting-rock-paper-scissors) to work on a new feature so you can work on your new code without fear.
+
+
+
+### Additional resources
+
+This section contains helpful links to related content. It isn't required, so consider it supplemental.
+
+- Stack Overflow has an [RSpec Mock Object example](http://stackoverflow.com/questions/3622604/rspec-mock-object-example).
+- Youtube has a [helpful video by Sandi Metz about Ruby testing](https://www.youtube.com/watch?v=URSWYvyc42M).
+- Tutorials Point has an article about [RSpec Writing Specs](https://www.tutorialspoint.com/rspec/rspec_writing_specs.htm).
diff --git a/ruby/testing_ruby_with_rspec/project_connect_four.md b/ruby/testing_ruby_with_rspec/project_connect_four.md
index f288435dcc4..bc82c999662 100644
--- a/ruby/testing_ruby_with_rspec/project_connect_four.md
+++ b/ruby/testing_ruby_with_rspec/project_connect_four.md
@@ -1,21 +1,6 @@
### Introduction
-A good way to get familiar with and begin contributing to a new project is to write tests for it. It's also the best way to become familiar with a new code base, something you'll have to do when you start working. It's pretty common for test code to ultimately take up twice as many lines of code as the actual project code!
-
-You still may feel shaky on RSpec at this point (which is totally normal), so let's go back in time and write tests for some of the code you've already done to build up a bit of muscle memory. If you've written a good batch, submit them below and we'll include them as part of the original project description to help future students!
-
-### Assignment
-
-
-
- 1. Clone our [ruby testing repo](https://github.com/TheOdinProject/ruby_testing) and complete the lessons in the spec folder.
- 1. Go back to the [Caesar Cipher Project](/lessons/ruby-caesar-cipher) and write tests for your code. It shouldn't take more than a half-dozen tests to cover all the possible cases. As always, use the git workflow you learned in [Revisiting Rock Paper Scissors](https://www.theodinproject.com/lessons/foundations-revisiting-rock-paper-scissors) to work on a new feature so you can work on your new code without fear.
- 1. Write tests for your [Tic Tac Toe project](/lessons/ruby-tic-tac-toe). In this situation, it's not quite as straightforward as just coming up with inputs and making sure the method returns the correct thing. You'll need to make sure the tests that determine victory or loss conditions are correctly assessed.
- 1. Start by writing tests to make sure players win when they should, e.g. when the board reads X X X across the top row, your `#game_over` method (or its equivalent) should trigger.
- 1. Test each of your critical methods to make sure they function properly and handle edge cases.
- 1. Use mocks/doubles to isolate methods to make sure that they're sending back the right outputs.
-
-
+At this point, you've written tests for older projects of yours, and have completed a plethora of other test-writign assignments to familiarize yourself with RSpec. You're now ready to create a new project with TDD in mind!
### Project: TDD Connect Four
@@ -27,7 +12,7 @@ The major difference here is that you'll be doing this TDD-style. So figure out
Only write exactly enough code to make your test pass. Oftentimes, you'll end up having to write two tests in order to make a method do anything useful. That's okay here. It may feel a bit like overkill, but that's the point of the exercise. Your thoughts will probably be something like "Okay, I need to make this thing happen. How do I test it? Okay, wrote the test, how do I code it into Ruby? Okay, wrote the Ruby, how can I make this better?" You'll find yourself spending a fair bit of time Googling and trying to figure out exactly how to test a particular bit of functionality. That's also okay... You're really learning RSpec here, not Ruby, and it takes some getting used to.
-### Assignment continued
+### Assignment
diff --git a/ruby/testing_ruby_with_rspec/revisiting_tictactoe.md b/ruby/testing_ruby_with_rspec/revisiting_tictactoe.md
new file mode 100644
index 00000000000..48358127137
--- /dev/null
+++ b/ruby/testing_ruby_with_rspec/revisiting_tictactoe.md
@@ -0,0 +1,23 @@
+### Introduction
+Now you have some experience with writing tests. Congratulations! Practice makes perfect, so here's another assignment.
+
+This time, you're going to go back to your Tic Tac Toe assignment and write tests for it.
+
+### Assignment
+
+
+
+ 1. Write tests for your [Tic Tac Toe project](/lessons/ruby-tic-tac-toe). In this situation, it's not quite as straightforward as just coming up with inputs and making sure the method returns the correct thing. You'll need to make sure the tests that determine victory or loss conditions are correctly assessed.
+ 1. Start by writing tests to make sure players win when they should, e.g. when the board reads X X X across the top row, your `#game_over` method (or its equivalent) should trigger.
+ 1. Test each of your critical methods to make sure they function properly and handle edge cases.
+ 1. Use mocks/doubles to isolate methods to make sure that they're sending back the right outputs.
+
+
+
+### Additional resources
+
+This section contains helpful links to related content. It isn't required, so consider it supplemental.
+
+- Stack Overflow has an [RSpec Mock Object example](http://stackoverflow.com/questions/3622604/rspec-mock-object-example).
+- Youtube has a [helpful video by Sandi Metz about Ruby testing](https://www.youtube.com/watch?v=URSWYvyc42M).
+- Tutorials Point has an article about [RSpec Writing Specs](https://www.tutorialspoint.com/rspec/rspec_writing_specs.htm).