Update contour notebook to clarify what data is used

[robbibt]

Proposed changes

This notebook didn't need to have Sentinel-2C added, but it was missing a mention at the top of the notebook of the Sentinel-2 product that is currently used.

Closes issues (optional)

• Closes Issue #000

Checklist

(Replace [ ] with [x] to check off)

• Notebook created using the DEA-notebooks template
• Remove any unused Python packages from Load packages
• Remove any unused/empty code cells
• Remove any guidance cells (e.g. General advice)
• Ensure that all code cells follow the PEP8 standard for code. The jupyterlab_code_formatter tool can be used to format code cells to a consistent style: select each code cell, then click Edit and then one of the Apply X Formatter options (YAPF or Black are recommended).
• Include relevant tags in the final notebook cell (refer to the DEA Tags Index, and re-use tags if possible)
• Clear all outputs, run notebook from start to finish, and save the notebook in the state where all cells have been sequentially evaluated
• Test notebook on both the NCI and DEA Sandbox (flag if not working as part of PR and ask for help to solve if needed)
• If applicable, update the Notebook currently compatible with the NCI|DEA Sandbox environment only line below the notebook title to reflect the environments the notebook is compatible with
• Check for any spelling mistakes using the DEA Sandbox's built-in spellchecker (double click on markdown cells then right-click on pink highlighted words). For example:

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[BexDunn]

looks like your testing suite is throwing some interesting errors @robbibt ? Should the tidal testing be running on this notebook?

[robbibt]

looks like your testing suite is throwing some interesting errors @robbibt ? Should the tidal testing be running on this notebook?

Yeah, something is wrong with the tests. We currently run the entire DEA Tools test suite for every PR, but perhaps we don't need to... I think it's OK for now, and I'll do some tweaks before we merge s2c_updates is merged to develop

[robbibt]

@BexDunn Can I please get a ✅? 🙏

[erialC-P]

Tick :)