Fix typos

[DimitriPapadopoulos]

TODO:

• Add unit tests and/or doctests in docstrings
• Add docstrings and API docs for any new/modified user-facing classes and functions
• New/modified features documented in docs/user-guide/*.rst
• Changes documented as a new file in changes/
• GitHub Actions have all passed
• Test coverage is 100% (Codecov passes)

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 94.54%. Comparing base (71cc0c2) to head (6f564d3).
⚠️ Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
src/zarr/core/array.py	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #3346   +/-   ##
=======================================
  Coverage   94.54%   94.54%           
=======================================
  Files          78       78           
  Lines        9419     9419           
=======================================
  Hits         8905     8905           
  Misses        514      514           

Files with missing lines	Coverage Δ
src/zarr/testing/stateful.py	98.29% <ø> (ø)
src/zarr/core/array.py	97.10% <0.00%> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[d-v-b]

why is the coverage report giving us false positives here

[DimitriPapadopoulos]

The single line of code I have modified to fix the the typo raises en exception and is not covered by a test.

[d-v-b]

The single line of code I have modified to fix the the typo raises en exception and is not covered by a test.

yes but your change did not reduce coverage, since that exception was not covered before. this seems like the important metric.