Fix hint wording in tutorial.md (#9867)
The tutorial hints that a change can be made that allows you to go back in time then click in the board to create a new entry, but the change is already present in the example code. This fix removes the hint and re-words the explanation of the change the example code is making.
Matthew Shotton committed
Sep 11, 2017 at 01:28 UTC
b80e3ad1f5861e502ce254098469a85162496163
1 file changed
+1
-3
docs/tutorial/tutorial.md
+1
-3
@@ -1038,7 +1038,7 @@ Add a method called `jumpTo` to the Game class:
1038
}
1039
```
1040
1041
-Then update `stepNumber` when a new move is made by adding `stepNumber: history.length` to the state update in Game's `handleClick`:
1041
+Then update `stepNumber` when a new move is made by adding `stepNumber: history.length` to the state update in Game's `handleClick`. We'll also update `handleClick` to be aware of `stepNumber` when reading the current board state so that you can go back in time then click in the board to create a new entry.:
1042
1043
```javascript{2,13}
1044
handleClick(i) {
@@ -1074,8 +1074,6 @@ Now you can modify Game's `render` to read from that step in the history:
1074
1075
If you click any move link now, the board should immediately update to show what the game looked like at that time.
1076
1077
-You may also want to update `handleClick` to be aware of `stepNumber` when reading the current board state so that you can go back in time then click in the board to create a new entry. (Hint: It's easiest to `.slice()` off the extra elements from `history` at the very top of `handleClick`.)
1078
-
1077
### Wrapping Up
1078
1079
Now, you've made a tic-tac-toe game that: