diff --git a/docs/plugins/AtlassianJiraServer.mdx b/docs/plugins/AtlassianJiraServer.mdx
index 9504f42aa..320cd0ec6 100644
--- a/docs/plugins/AtlassianJiraServer.mdx
+++ b/docs/plugins/AtlassianJiraServer.mdx
@@ -209,9 +209,9 @@ https://jira.company.com/jira
 https://jiraeu.company.com
 ```
 
-3. Verify the project key in JIRA Server is correct. Please fill in the Project key field with project key-value, e.g. project ABC-DEF has key ABCDEF.
+2. Verify the project key in JIRA Server is correct. Please fill in the Project key field with project key-value, e.g. project ABC-DEF has key ABCDEF.
 
-4. Verify the username and password data. Make sure, that the login name and not the email are in the username field. In case all the data above is correct, but the error appears again, check whether the user's credentials to JIRA Server are not expired. As far as JIRA Server sends the request in HTML format, we are not able to display the real reason for the error. To check and/or resolve the issue, please do the next steps:
+3. Verify the username and password data. Make sure, that the login name and not the email are in the username field. In case all the data above is correct, but the error appears again, check whether the user's credentials to JIRA Server are not expired. As far as JIRA Server sends the request in HTML format, we are not able to display the real reason for the error. To check and/or resolve the issue, please do the next steps:
 
     *    Open JIRA Server page
     *    Log in to JIRA Server with domain credentials using basic authorization (i.e., fill in user's login name and password into the fields)
@@ -220,7 +220,7 @@ https://jiraeu.company.com
     *    Submit the credentials again
     *    Now try to establish the connection to JIRA Server on the ReportPortal project.
 
-5. SSL instance of JIRA (even cloud version) can be accessed by JIRA API token, used instead of a password.
+4. SSL instance of JIRA (even cloud version) can be accessed by JIRA API token, used instead of a password.
    After you have connected Jira and our test automation results dashboard, you can choose an issue type that you will be able to add to Jira during the “Post Issue” operation.  Also, the user can add predefined fields that the user can fill.
 
 ## Post issue to Atlassian Jira Server
diff --git a/docs/reportportal-configuration/HowToGetAnAccessTokenInReportPortal.mdx b/docs/reportportal-configuration/HowToGetAnAccessTokenInReportPortal.mdx
index 039e1c2c5..775130c0e 100644
--- a/docs/reportportal-configuration/HowToGetAnAccessTokenInReportPortal.mdx
+++ b/docs/reportportal-configuration/HowToGetAnAccessTokenInReportPortal.mdx
@@ -53,7 +53,7 @@ Another method involves using the API Key found on the user's Profile page.
 
 The API Key is a unique token that grants access to the ReportPortal REST API.
 
-To use it, log in and navigate to the Profile page, then find the API Keys tab. If you've previously created a token, it now has been converted to a Legacy API Key at the moment of migration to newest version and it remains valid and operational.
+To use it, log in and navigate to the Profile page, then find the API Keys tab. If you’ve previously integrated agents using UUID, it has been converted to a Legacy API Key at the moment of migration to newest version and it remains valid and operational.
 
 :::note
 It will continue to work even if you generate new API Keys.