Update issue templates

.github/ISSUE_TEMPLATE/feature_request.md

@@ -13,7 +13,7 @@ Before filing a feature request, please consider if it fits the scope of the pac
 
 1. Do you want to hack apart the string of LilyPond syntax generated by `phrase()` ad hoc? Why? Can your problem be reformulated?
 
-`phrase()` is not intended to create arbitrary LilyPond markup. You may want to consider just using LilyPond directly. The `lilypond()` function exists so that you can create a LilyPond file rather than rendering it to sheet music. This is so that you can spot edit it after creating it if `phrase()` cannot meet your needs. There is a lot in LilyPond that tabr will never do. If your needs are great, you may be leaning on tabr too much. If there is a need to manipulate the string result of phrase, this speaks to a broader more fundamental problem somewhere else, which may not may not be worth resolving with tabr, but the answer is not to do LilyPond syntax post-processing.
+`phrase()` is not intended to create arbitrary LilyPond markup. You may want to consider just using LilyPond directly. The `lilypond()` function exists so that you can create a LilyPond file rather than rendering it to sheet music. This is so that you can spot edit it after creating it if `phrase()` cannot meet your needs. There is a lot in LilyPond that tabr will never do. If your needs are great, you may be leaning on tabr too much. If there is a need to manipulate the string result of phrase, this speaks to a broader more fundamental problem somewhere else, which may or may not be worth resolving with tabr, but the answer is not to do LilyPond syntax post-processing.
 
 2. Do you want your own unique music syntax?