[dolphinscheduler] 14/20: [doc] Correct E2E Doc, fix WorkerGroupPage typo (#11629)

[zh...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

zhongjiajie pushed a commit to branch 3.0.1-prepare
in repository https://gitbox.apache.org/repos/asf/dolphinscheduler.git

commit f41af79ef68f9f45283b90b0a164a343d053d629
Author: 旺阳 <qi...@cisco.com>
AuthorDate: Sun Aug 28 17:44:06 2022 +0800

     [doc] Correct E2E Doc, fix WorkerGroupPage typo (#11629)
    
    (cherry picked from commit 6e4d974b91a38047d0073a36944817a0cd21a6fd)
---
 docs/docs/en/contribute/e2e-test.md | 2 +-
 docs/docs/zh/contribute/e2e-test.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/docs/en/contribute/e2e-test.md b/docs/docs/en/contribute/e2e-test.md
index 2fd853db93..82affec552 100644
--- a/docs/docs/en/contribute/e2e-test.md
+++ b/docs/docs/en/contribute/e2e-test.md
@@ -74,7 +74,7 @@ During the test process, we only test the elements we need to focus on, not all
 
 In addition, during the testing process, the elements are not manipulated directly. The general choice is to package the corresponding methods to achieve the effect of reuse. For example, if you want to log in, you input your username and password through the `public TenantPage login()` method to manipulate the elements you pass in to achieve the effect of logging in. That is, when the user finishes logging in, he or she jumps to the Security Centre (which goes to the Tenant Management p [...]
 
-The goToTab method is provided in SecurityPage to test the corresponding sidebar jumps, which include TenantPage, UserPage and WorkerGroupPge and QueuePage. These pages are implemented in the same way, to test that the form's input, add and delete buttons return the corresponding pages.
+The SecurityPage provides goToTab methods to test the corresponding sidebar jumps, mainly including TenantPage, UserPage, WorkerGroupPage and QueuePage. These pages are implemented in the same way, mainly to test whether the input, add and delete buttons of the form can return to the corresponding page.
 
 ```java
  public <T extends SecurityPage.Tab> T goToTab(Class<T> tab) {
diff --git a/docs/docs/zh/contribute/e2e-test.md b/docs/docs/zh/contribute/e2e-test.md
index 69535536e9..13b8d4ab1e 100644
--- a/docs/docs/zh/contribute/e2e-test.md
+++ b/docs/docs/zh/contribute/e2e-test.md
@@ -73,7 +73,7 @@ public final class LoginPage extends NavBarPage {
 
 此外，在测试过程中，并不会直接去操作元素，一般选择封装对应的方法，以达到复用的效果。例如想要登录的话，直接传入用户名和密码，通过 `public TenantPage login()` 方法去操作所传入的元素，从而达到实现登录的效果，即当用户完成登录之后，跳转到安全中心（默认进入到租户管理页面）。
 
-在安全中心页面（SecurityPage）提供了 goToTab 方法，用于测试对应侧栏的跳转，主要包括：租户管理（TenantPage）、用户管理（UserPage）、工作组管理（WorkerGroupPge）和队列管理（QueuePage）。这些页面的实现方式同理，主要测试表单的输入、增加和删除按钮是否能够返回出对应的页面。
+在安全中心页面（SecurityPage）提供了 goToTab 方法，用于测试对应侧栏的跳转，主要包括：租户管理（TenantPage）、用户管理（UserPage）、工作组管理（WorkerGroupPage）和队列管理（QueuePage）。这些页面的实现方式同理，主要测试表单的输入、增加和删除按钮是否能够返回出对应的页面。
 
 ```java
  public <T extends SecurityPage.Tab> T goToTab(Class<T> tab) {