based on https://chat.civicrm.org/civicrm/pl/etog75icwjywt84sxtw11fumoh

The phrase originated in one context (i.e.  discussing a change in the
version-numbering pattern).  In the context of `info.xml` docs, it seemed
helpful to use more concrete wording ("Because 4.7.x and 5.x are
substantively the same series...").

Updating docs to reflect changes made here: dev/release#1 (comment 2843)

Two arrows were being interpreted as two layers of quotes. I removed one of them. Then I thought, actually, these are not quotes. Maybe we should remove move. And maybe just having them on their on paragraph without any quotes is good enough. I am shying away from using boxes for this since to avoid box fatigue but would be interested in some opinions on the house style.

We ha one "Generating a skeletal extension" and one "Add features"

Changed `civix generate:custom-data` to `civix generate:custom-xml` as the former is incorrect. Also corrected grammar in subheading "Extending a subtype".

I removed this sentence because I don't think it's accurate.

We have these review criteria:
https://docs.civicrm.org/extensions/lifecycle/#review-criteria

The criteria do say that you can't use PHP overrides. But there are
other interfaces (like BAO functions for example) that are not in the
"supported methods" list but also not prohibited based on the extension
review criteria.

No content edits here. Just a direct copy paste.

Per discussion in documentation channel I think we need to document what methods are considered supported / expected to be stable. The last 4 items in this list have not been previously documented as a supported way to interact with CiviCRM so may be subject to discussion

Page should not link to itself.

ref:
https://github.com/civicrm/civicrm-wordpress/pull/112

I'm not sure if this has only come about because of my ineptitude (i.e. whether an Entity would always have the same name as the extension), but I found that I couldn't find the files referred to because my Entity and my Extension had different names.

Would that be bad practice on my part? (it would be good to know as I'm very new to coding)

Either way, I think this may be more accurate... rest is up to you.

Cheers,
M.

Find/replace `(?<=\w) {2,}` with ` `

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Reading for content; editing for consistency.

Previously it read that you only needed to create a release on *subsequent* releases, but my experience was that the extension was not available until the initial release was made also. Rewrote to clarify this.

Also made a few additions to inline docs on the create a release node page. These can be recorded over in CiviCRM.org website repo via Features.

Refs #323.