docs: Update basic usage with better wording for examples.

[nfelt14]

Proposed changes

Update the wording in the basic usage document to better indicate how to configure devices.

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Documentation update (an update to enhance the user experience when reading through the docs)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have followed the guidelines in the CONTRIBUTING document
• I have signed the CLA
• I have checked to ensure there aren't other open Pull Requests for the same update/change
• I have performed a self-review of my code
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• Basic linting passes locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have added necessary documentation (if appropriate)
• I have updated the Changelog with a brief description of my changes

[codecov]

Codecov Report

Merging #83 (5a1f510) into main (a38bd8c) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##              main       #83   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          168       168           
  Lines         3768      3768           
  Branches       646       646           
=========================================
  Hits          3768      3768           

Files	Coverage Δ
.../tm_devices/driver_mixins/class_extension_mixin.py	100.00% <100.00%> (ø)

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more