Address feedback in #1670

[IEvangelist]

Summary

• Move integration listing under cloud-native content.
• Remove note about provisioning.
• Correct details about which type is extended.
• Add more links back to app host content.
• Added terminology bookmark.
• Edit pass.

Fixes #1670.

---

Internal previews

📄 File	🔗 Preview link
docs/fundamentals/app-host-overview.md	docs/fundamentals/app-host-overview
docs/fundamentals/health-checks.md	docs/fundamentals/health-checks
docs/fundamentals/integrations-overview.md	docs/fundamentals/integrations-overview
docs/fundamentals/service-defaults.md	docs/fundamentals/service-defaults
docs/fundamentals/setup-tooling.md	docs/fundamentals/setup-tooling

[DamianEdwards]

In the cloud-native features section, we should consider removing the orchestration paragraph completely, as it currently reads as though the app host provides orchestration in the cloud rather than being for dev time only.

We should consider removing "cloud-native" from the section altogether actually, and focus more on what is actually added, i.e. service discovery and service defaults.

[IEvangelist]

In the cloud-native features section, we should consider removing the orchestration paragraph completely, as it currently reads as though the app host provides orchestration in the cloud rather than being for dev time only.

We should consider removing "cloud-native" from the section altogether actually, and focus more on what is actually added, i.e. service discovery and service defaults.

To clarify, you're advocating for deleting all the Cloud-native content and its subsections?

Delete Cloud-native, Observability and telemetry, Health checks, and Resiliency sections?

[DamianEdwards]

To clarify, you're advocating for deleting all the Cloud-native content and its subsections?

Delete Cloud-native, Observability and telemetry, Health checks, and Resiliency sections?

Re-frame, rather than delete. No "Cloud-native" heading or positioning.

[tdykstra]

LGTM