Cleanup/kedro notebook instructions

[ethanknights]

Description

Minor language fixes in the kedro notebook example.

Development notes

Changes for making styling consistent across README/notebook docs.

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

• Read the contributing guidelines
• Signed off each commit with a Developer Certificate of Origin (DCO)
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added a description of this change in the RELEASE.md file
• Added tests to cover my changes
• Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

[merelcht]

Thank you @ethanknights, looks good to me ⭐

[astrojuanlu]

Thank you @ethanknights !

Wondering how are you finding Kedro so far? 😊

[ethanknights]

Thanks both!
Yeah @astrojuanlu - early days, but I think the opinionated project structure/node format scaffolding seems a good way for (trying!) to keep mlflow experimentations a bit tamer (e.g. rather than simply forcing them into cookiecutter structures etc).
Thanks for your work on this tool.