Doc fix: Do not mention next project in book/guessing-game

[deepak]

fixes #32936

[rust-highfive]

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @Manishearth (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

[Manishearth]

Perhaps remove this entirely?

[deepak]

@Manishearth as a beginner, I like the old one better. It informs me that:

1. I have successfully completed a challenge. feels good
2. I have learnt a bunch of stuff. feels good again
3. I can look forward to another problem. looking forward to feeling good again

Just telling me that i have completed a challenge feels worse by comparison
but that is just me probably

I would have liked another problem to go through. but when will that stop :-)

[Manishearth]

Yes, but it seems a bit out of place. The chapter was already concluded with the previous sentence. If this could be moved above and edited to make more sense that would be fine.

[deepak]

@Manishearth ok. fixing it

[Manishearth]

@bors r+ rollup

thanks!

[bors]

📌 Commit a40629d has been approved by Manishearth

[bors]

⌛ Testing commit a40629d with merge c7b1d45...

[bors]

💔 Test failed - auto-win-gnu-32-opt

[alexcrichton]

@bors: retry

On Thu, Apr 14, 2016 at 1:02 PM, bors [email protected] wrote:

[image: 💔] Test failed - auto-win-gnu-32-opt
http://buildbot.rust-lang.org/builders/auto-win-gnu-32-opt/builds/3808

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#32937 (comment)