<!-- Choose one of the following prefixes for the title of your PR:

     [ENH] for enhancements
     [FIX] for bug fixes
     [TST] for new or updated tests
     [DOC] for new or updated documentation
     [STY] for stylistic changes
     [REF] for refactoring existing code

     If your PR is not yet ready to be merged, click on the dropdown arrow next to the
     "Create pull request" button and choose "Create draft pull request" instead.
     This will put your PR in draft state and block merging until you change the status
     of the PR to "Ready for review".
-->

## Description

Please include a summary of the change and which issue it closes below. Include relevant motivation and context.

Closes #(issue)

## Type of Change

Please delete options that are not relevant.

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Documentation change

## Checklist

- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] 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

For detailed information on these and other aspects, see the contribution guidelines: https://pulse2percept.readthedocs.io/en/latest/developers/contributing.html

<!-- Choose one of the following prefixes for the title of your PR:

     [ENH] for enhancements
     [FIX] for bug fixes
     [TST] for new or updated tests
     [DOC] for new or updated documentation
     [STY] for stylistic changes
     [REF] for refactoring existing code
     [MNT] for packaging/maintenance updates 

     If your PR is not yet ready to be merged, click on the dropdown arrow next to the
     "Create pull request" button and choose "Create draft pull request" instead.
     This will put your PR in draft state and block merging until you change the status
     of the PR to "Ready for review".
-->

## Description

Please include a summary of the change and which issue it closes below. Include relevant motivation and context.

Closes #(issue)

## Type of Change

Please delete options that are not relevant.

- [ ] Bug fix (non-breaking change which fixes an issue)
- [ ] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
- [ ] Documentation change

## Checklist

- [ ] I have performed a self-review of my own code
- [ ] I have commented my code, particularly in hard-to-understand areas
- [ ] I have made corresponding changes to the documentation
- [ ] 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

For detailed information on these and other aspects, see the contribution guidelines: https://pulse2percept.readthedocs.io/en/latest/developers/contributing.html

Add abbreviation for maintenance commits
[DOC] Add abbreviation for maintenance commits