In some place of this documentation, a CR is showed with jaeger UI enabled (not gateway) and some steps to verify In one of those steps in mentions

'Select Log In With OpenShift to use your cluster administrator credentials for the web console.'

Which is incorrect because the only way to have authentication in that way is with the gateway. We need to fix that.

In installing Tempo operator from [web console|https://docs.openshift.com/container-platform/4.15/observability/distr_tracing/distr_tracing_tempo/distr-tracing-tempo-installing.html#distr-tracing-tempo-install-web-console_dist-tracing-tempo-installing).  The step

'Select the Tempo Operator that is OpenShift Operator for Tempo → Install → Install → View Operator.' 

'Should be 'Select the Tempo Operator that is provided by Red Hat → Install → Install → View Operator.'

In the same Tempo web install document. This section should also include enabling the operator monitoring like below.

This installs the Operator with the default presets:

• Update channel → stable

• Installation mode → All namespaces on the cluster

• Installed Namespace → openshift-tempo-operator

• Select Enable Operator recommended cluster monitoring on this Namespace

• Update approval → Automatic

In installing Tempo Operator from CLI, the Access the Tempo console:can be simplified. The point
a. Query the route details by running the following command: 

$ export TEMPO_URL=$(oc get route -n <control_plane_namespace> tempo -o jsonpath='{.spec.host}')

Can simply be oc get route