fix: Add IRSA cross-account deployment guide

docs/operator-guide/cd/deploy-application-in-remote-cluster-via-irsa.md

@@ -28,9 +28,9 @@ To start using this approach, you need to have OIDC (OpenID Connect) already con
 Cross-account interaction is performed through IRSA with a two-tiered IAM role setup:
 
 - In AWS Account A, the EKS cluster runs a kuberocketci cd-pipeline-operator with service account.
-- This service account obtains temporary credentials through IRSA, which are associated with the AWSIRSA_\{cluster_name\}_CDPipelineOperator role.
-- AWSIRSA_\{cluster_name\}_CDPipelineOperator can then assume the AWSIRSA_\{cluster_name\}_CDPipelineAgent role in AWS Account B.
-- AWSIRSA_\{cluster_name\}_CDPipelineAgent configures the environment (Stage) by creating namespaces, generating service accounts, copying secrets, and preparing for deployment.
+- This service account obtains temporary credentials through IRSA, which are associated with the `AWSIRSA_\{cluster_name\}_CDPipelineOperator` role.
+- `AWSIRSA_\{cluster_name\}_CDPipelineOperator` can then assume the `AWSIRSA_\{cluster_name\}_CDPipelineAgent` role in AWS Account B.
+- `AWSIRSA_\{cluster_name\}_CDPipelineAgent` configures the environment (Stage) by creating namespaces, generating service accounts, copying secrets, and preparing for deployment.
 
 ### Required IAM Roles, and polices for KRCI