Example of an email service documentation misleading uid

[koyanyaroo]

What does it do?

If I understand correctly The code example of an email service documentation is misleading

so I assume createCoreService('api::email.email') instead of createCoreService('api::restaurant.restaurant')

according to // path: ./src/api/email/services/email.js
and strapi.service('api::apiName.serviceName');

and

createCoreController('api::user.user') instead of createCoreController('api::restaurant.restaurant')

according to // path: ./src/api/user/controllers/user.js
and strapi.controller('api::api-name.controller-name');

Why is it needed?

If my understanding is correct, then it's maybe need to be changed

Related issue(s)/PR(s)

Let us know if this is related to any issue/pull request

[strapi-cla]

All committers have signed the CLA.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/strapijs/documentation/415xGiPFQMeFCgijPPn4H7pN9PBv
✅ Preview: https://documentation-git-fork-koyanyaroo-fix-email-ser-454e5f-strapijs.vercel.app

[derrickmehaffy]

duplicate of #727

[pwizla]

Thank you for your contribution @koyanyaroo !
FYI this pull request is a duplicate of #727. You might want to follow further progress on this topic on the other PR.

We will probably keep api::restaurant.restaurant here. We think this part of the documentation might be misunderstood and we are working with back-end developers to improve these examples, so our readers get a better understanding. This PR will probably stay closed but I will get back to you once we improve this part of the documentation 🙂