Closed luizaandrade closed 4 years ago
This PR will conflict with PR #375. I guess the best solution is to merge this PR into 375 (or the other way around, before merging into develop.)
This PR will conflict with PR #375. I guess the best solution is to merge this PR into 375 (or the other way around, before merging into develop.)
Yes. I am working on this branch currently as a review. Don't worry about the intro conflict; it is only two paragraphs and easy to resolve.
ok, if you are working on this now, then I will review later. I need to head out soon and I do not want to create more conflicts.
I made small edits for clarity and updated section and chapter name. This is good from my side.
⚠️ for some reason this is showing up as a really gnarly merge. I don't know why it is so bad. But let's get the outstanding things in this PR sorted, and then my instinct will be to accept all content as-is from this branch and then go back and make sure the intro is correct.
Resolves #347