[docs] make update-beats-docs

[bmorelli25]

Updating Beats documentation. Most of these are small grammar or formatting changes.

I'm curious about the new roles added in the table to the securing-beats.asciidoc page. Are these relevant to APM Server:

apm-server/docs/copied-from-beats/security/securing-beats.asciidoc

Lines 55 to 84 in 30ba8f0

	[options="header"]
	|=======
	|Feature | Role
	|Send data to a secured cluster | ++{beat_default_index_prefix}_writer++ footnoteref:[noteA,These roles are user-defined.]
	ifeval::["{beatname_lc}"=="filebeat"]
	|Run Filebeat modules | ++{beat_default_index_prefix}_writer++ footnoteref:[noteA]
	endif::[]
	|Load index templates | ++{beat_default_index_prefix}_writer++ footnoteref:[noteA] and `kibana_user`
	ifndef::no_dashboards[]
	|Load {beatname_uc} dashboards into {kib} | ++{beat_default_index_prefix}_writer++ footnoteref:[noteA] and `kibana_user`
	endif::[]
	ifdef::has_ml_jobs[]
	|Load machine learning jobs | `machine_learning_admin`
	endif::[]
	|Read indices created by {beatname_uc} | ++{beat_default_index_prefix}_reader++ footnoteref:[noteA]
	ifndef::no_dashboards[]
	|View {beatname_uc} dashboards in {kib} | `kibana_user`
	endif::[]
	ifdef::has_central_config[]
	|Store and manage configurations in a central location in {kib} | `beats_admin`
	endif::[]
	ifndef::no_ilm[]
	|Load index lifecycle policies and use index lifecycle management | +{beatname_lc}_ilm+ footnoteref:[noteA]
	endif::[]
	|=======
	To create the user-defined roles shown here, see <<beats-basic-auth>> and
	<<beats-user-access>>. You may want to define additional roles to provide more
	restrictive access.

If someone could take a look when they have time, that'd be 🔥

I'd like to backport these to 7.0 (#1954) and 7.x (#1955)

[graphaelli]

The _security url updates are 👍.

The "load dashboard" and "ilm" roles don't make sense for apm-server. The read indices is covered by the built-in apm_user role. The remaining entries, including the dashboard-viewing role, make sense to me me to keep.

[bmorelli25]

Great, thanks @graphaelli! We had almost everything correct then. I re-added View APM Server dashboards in Kibana, and changed Read indices created by APM Server to the new apm_user role. Here's what that page renders as now:

---