Add prerequisite and fix command line in Flatpak (#3914)

Author: bangelic

guides/common/modules/proc_enabling-the-flatpak-remote.adoc

@@ -67,6 +67,9 @@ $ hammer flatpak-remote remote-repository mirror \
 --id=_My_Remote_Repo_ID_ \
 --product-id=_{Project}_Product_ID_
 ----
++
+The `--id` in this command refers to the Flatpak remote repository ID, not the standard {Project} repository ID.
++
 You can view the repository under the selected product in {ProjectWebUI}.
 Set the *Include Tags* field to *latest*.
 . Synchronize the {Project} repository:
@@ -75,3 +78,5 @@ Set the *Include Tags* field to *latest*.
 ----
 $ hammer repository sync --id=_My_Repo_ID_
 ----
++
+The `--id` in this command refers to the standard {Project} repository ID, not the Flatpak remote repository ID.

guides/common/modules/proc_importing-and-exporting-content-to-project-server-for-flatpak.adoc

@@ -34,7 +34,7 @@ $ flatpak remote-add --authenticator-name=org.flatpak.Authenticator.Oci katello
 +
 [options="nowrap", subs="+quotes,verbatim,attributes"]
 ----
-$ podman login
+$ podman login _{foreman-example-com}_
 ----
 . Install your application.
 For example, to install the Mozilla Firefox Flatpak:

guides/common/modules/proc_installing-flatpak-applications-on-project-hosts.adoc

@@ -6,10 +6,14 @@
 Use the command line to install selected applications from the enabled Flatpak remotes.
 
 .Prerequisites
-* Install Flatpak.
+* Flatpak is installed on the host.
 ifdef::satellite[]
-* Enable the {Team} Flatpak remote.
+* The {Team} Flatpak remote is enabled.
 endif::[]
+* Ensure that Podman is installed on the host.
+* To install Flatpak applications from {Project}, ensure that your {Project} account has the `view_lifecycle_environments`, `view_products`, and `view_content_views` permissions, unless the lifecycle environment allows unauthenticated pull.
+* Your {Project} account has a role that grants the `create_personal_access_tokens` permission to generate an access token for authentication.
+The token generates automatically when you run `podman login`.
 
 .Procedure
 . On the managed host, add your {ProjectServer} as a Flatpak remote:
@@ -22,7 +26,7 @@ $ flatpak remote-add --authenticator-name=org.flatpak.Authenticator.Oci katello
 +
 [options="nowrap", subs="+quotes,verbatim,attributes"]
 ----
-$ podman login
+$ podman login _{foreman-example-com}_
 ----
 . Install your application.
 For example, to install the Mozilla Firefox Flatpak:

guides/common/modules/proc_setting-up-flatpak-remote-for-smartproxy.adoc

@@ -26,7 +26,7 @@ $ flatpak remote-add --authenticator-name=org.flatpak.Authenticator.Oci katello
 +
 [options="nowrap", subs="+quotes,verbatim,attributes"]
 ----
-$ podman login
+$ podman login _{foreman-example-com}_
 ----
 For more information about logging in using Podman, see xref:Configuring_podman_to_trust_the_CA_{context}[].
 +

guides/common/modules/proc_using-container-registries.adoc

@@ -12,6 +12,8 @@ For more information about OCI, see link:https://opencontainers.org/[Open Contai
 * Ensure that a product exists before pushing a repository.
 For more information, see xref:Creating_a_Custom_Product_{context}[].
 * To pull content from {Project}, ensure that your {Project} account has the `view_lifecycle_environments`, `view_products`, and `view_content_views` permissions, unless the lifecycle environment allows unauthenticated pull.
+* Your {Project} account has a role that grants the `create_personal_access_tokens` permission to generate an access token for authentication.
+The token generates automatically when you run `podman login`.
 
 ifndef::orcharhino[]
 .Container registries on {SmartProxies}
@@ -36,7 +38,7 @@ If you use the ID-based schema, pull using IDs.
 +
 [options="nowrap", subs="+quotes,attributes"]
 ----
-# podman login {foreman-example-com}
+# podman login _{foreman-example-com}_
 ----
 
 * Listing container images: