doc: remove "feature branch" jargon
Checklist
-
make -j4 test
(UNIX), orvcbuild test nosign
(Windows) passes -
documentation is changed or added -
commit message follows commit guidelines
Affected core subsystem(s)
doc
Description of change
In the context of the CONTRIBUTING.md document, there is no advantage to describing the branch as a "feature branch" and the term may be confusing. Just refer to it as a branch.
Context for the curious: The phrase "feature branch" in CONTIRUBTING.md confused someone I was assisting today. It occured to me that the word "feature" doesn't add anything and can be confusing. ("I'm doing a bug fix so I don't need to create a feature branch, right?")
/cc @thecoolestguy