Update README.md

[EvaMaeRey]

micro suggestion... use labs instead of xlab ylab in example?

Description

I have a preference for using labs() generally, this makes it easier to remember how to make a quick legend label change too.

Proposed Changes

List changes below in bullet format:

• xlab() -> labs(x =)

PR Checklist

Before submitting this PR, please check and verify below that the submission meets the below criteria:

• New/revised functions have associated tests
• New/revised functions that update downstream outputs have associated static testing files (.RDS) updated under inst/testdata/create_test_data.R
• New/revised functions use appropriate naming conventions
• New/revised functions don't repeat code
• Code changes are less than 250 lines total
• Issues linked to the PR using GitHub's list of keywords
• The appropriate reviewer is assigned to the PR
• The appropriate developers are assigned to the PR
• Pre-release package version incremented using usethis::use_version()

Code Review

This section to be used by the reviewer and developers during Code Review after PR submission

Code Review Checklist

• I checked that new files follow naming conventions and are in the right place
• I checked that documentation is complete, clear, and without typos
• I added/edited comments to explain "why" not "how"
• I checked that all new variable and function names follow naming conventions
• I checked that new tests have been written for key business logic and/or bugs that this PR fixes
• I checked that new tests address important edge cases

[rsh52]

micro suggestion... use labs instead of xlab ylab in example?

@EvaMaeRey Sure thing! Thank you for the suggestion. I will also update the README so it includes the arrow_data that I left out.