Update parallelism example

[skrawcz]

Updates parallelism example + some minor typo fixes in docs.

Changes

• changes doc strings
• parallelism example notebook

How I tested this

• locally

Notes

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 76cb63a in 12 seconds

More details

• Looked at 102 lines of code in 3 files
• Skipped 1 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. burr/core/parallelism.py:335

• Draft comment:
  Consider using list[str] instead of List[str] for consistency with other parts of the file. This change is applicable in other parts of the file as well, such as lines 451 and 455.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The change from List[str] to list[str] is consistent with Python 3.9+ type hinting standards. However, the change is not applied consistently across the file.

Workflow ID: wflow_WMUk4zlSQoJD1tXh

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[github-actions]

A preview of is uploaded and can be seen here:

✨ https://burr.dagworks.io/pull/431 ✨

Changes may take a few minutes to propagate. Since this is a preview of production, content with draft: true will not be rendered. The source is here: https://github.com/DAGWorks-Inc/burr/tree/gh-pages/pull/431/