fix: update docs to reflect correct record handling

[MehulKChaudhari]

This PR will fix the bug in documentation in http://localhost:4200/#updating-data__create-record where we use recordIdentifierFor(data.record) in request body but since data.record is already an identifier removed it.

Ref discussion on discord: https://discord.com/channels/480462759797063690/486549196837486592/1342571022221840555

Changes:

• Removed recordIdentifierFor(data.record) since data.record is already an identifier.
• Updated ember serve to npm run start in contributing.md as per RFC #Standardize use of scripts in package.json for common tasks emberjs/rfcs#831.
• Fixed a typo in the Creating/Updating Data section.

[netlify]

✅ Deploy Preview for request-service-cheat-sheet ready!

Name	Link
🔨 Latest commit	597ad09
🔍 Latest deploy log	https://app.netlify.com/sites/request-service-cheat-sheet/deploys/67bad07f3760760008301acb
😎 Deploy Preview	https://deploy-preview-18--request-service-cheat-sheet.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[runspired]

this one too keeps the recordIdentifierFor usage

[runspired]

mostly gets it to the right place, a couple of overly aggressive changes to backout.

Basically:

• inside a handler, the builders will have given you an identifier already
• outside a handler, where you have the record instance, you need to get the identifier

[MehulKChaudhari]

mostly gets it to the right place, a couple of overly aggressive changes to backout.

Basically:

• inside a handler, the builders will have given you an identifier already
• outside a handler, where you have the record instance, you need to get the identifier

Got it. Thanks for explaining :)