FF Project issues template (#32828)

* FF Project issues template

* CODEOWNERS - MDN team own issues

---------

Co-authored-by: Brian Thomas Smith <[email protected]>

.github/CODEOWNERS

@@ -70,6 +70,8 @@
 # owners specified here.
 # ----------------------------------------------------------------------------
 /.github/     @mdn/core-dev
+## Issue templates
+/.github/ISSUE_TEMPLATE/ff-project-issue.md    @mdn/core-yari-content
 /*            @mdn/core-dev
 /*.md         @mdn/core-yari-content
 # These are @mdn-bot because the auto-merge GHA workflow uses the PAT of this account.

.github/ISSUE_TEMPLATE/ff-project-issue.md

@@ -6,7 +6,7 @@ assignees:
 title: ""
 ---
 
-## Acceptance Criteria
+## Acceptance criteria
 
 - [ ] The listed features are documented sufficiently on MDN
 - [ ] BCD is updated
@@ -16,8 +16,8 @@ title: ""
 ### For folks helping with Firefox related documentation
 
 - [ ] Set bugs to `dev-doc-complete`
-- [ ] Add entry to Firefox release notes if feature is enabled in release
-- [ ] Add entry to Firefox experimental features page if feature is not yet enabled in release
+- [ ] Add entry to Firefox release notes for enabled/preview features
+- [ ] Add/remove entry to Firefox experimental features page for preference/released features
 
 ## Features to document
 
@@ -26,5 +26,3 @@ title: ""
 ## Other
 
 - [ ] Check content open issues to see if any pertain to the subject matter. If there are any that can be closed because of the work, do so. If there are any that can be fixed relatively quickly because of the knowledge from completing this issue and you have time, feel free to go ahead and fix them.
-- [ ] Check if glossary updates are required for the feature you're documenting - whether an existing term needs to be updated or a new term should be added.
-- [ ] Check if BCD update means that content pages need to have experimental markup removed or deprecated markup added (front matter tags and macros).