fix(core): change ng to nx

[ammanvedi]

The command ng is incorrect it should be nx

Current Behavior

The command in generated readme says ng

Expected Behavior

It should say nx

[nx-cloud]

☁️ Nx Cloud Report

CI ran the following commands for commit b767dc7. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 20 targets

• nx affected --target=e2e --base=7d487fe3d53266c3736dadeac00f1f4db7145a93 --head=b767dc79c9e0cb6f86a090add6c6271c74c68d68 --exclude=e2e-react-native,e2e-detox --parallel=1
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx run-many --target=build --all --parallel=8
• nx affected --target=test --base=7d487fe3d53266c3736dadeac00f1f4db7145a93 --head=b767dc79c9e0cb6f86a090add6c6271c74c68d68 --parallel=1
• nx affected --target=build --base=7d487fe3d53266c3736dadeac00f1f4db7145a93 --head=b767dc79c9e0cb6f86a090add6c6271c74c68d68 --parallel=3
• nx build typedoc-theme

---

Sent with 💌 from NxCloud.

[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/nrwl/nx-dev/AZHGseR1wHff65FrHpzVm4QysQnX
✅ Preview: Canceled

[meeroslav]

Thank you @ammanvedi!

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.