Renamed as_bytes_mut to as_mut_bytes

[dorryspears]

Closes #253

I saw this in the nice-to-haves in #671, so I thought I would knock it out.

[jswrenn]

Can you just edit your commit message to:

Renamed `as_bytes_mut` to `as_mut_bytes`

[dorryspears]

@jswrenn Renamed commit

[jswrenn]

Whoops, sorry for the inconvenience, but I didn't mean for you to edit out the reference to the issue. The full message should be something like this:

Renamed `as_bytes_mut` to `as_mut_bytes`

Fixes #253

[joshlf]

Whoops, sorry for the inconvenience, but I didn't mean for you to edit out the reference to the issue. The full message should be something like this:

Renamed `as_bytes_mut` to `as_mut_bytes`

Fixes #253

...and if you want to be really pedantic with our commit message guidelines, it should be "Rename as_bytes_mut..." rather than "Renamed as_bytes_mut..." (past tense). To be clear, we will absolutely still merge this without that tiny change, but while we're nitpicking 😛

[dorryspears]

@jswrenn @joshlf I appreciate the guidance, I am new to zerocopy, learning the ways 🎉
Changed commit message to include the issue and reflect the grammar from the guidelines

[jswrenn]

One last tweak: Just put a double newline between the subject and 'Fixes', like this:

Renamed `as_bytes_mut` to `as_mut_bytes`

Fixes #253

Right now, they're all on one line.

[jswrenn]

We do this because git treats the first line of the commit message as its subject; see here: https://github.com/google/zerocopy/commit/bff9148ad8e7bf034e0992a1f8b4bf9553f2e386.patch

[dorryspears]

@jswrenn fixed commit message

[joshlf]

Thanks for this, @dorryspears !