Principal
|
- - Include or Exclude
- Cloud service user, Federated user
- If you select Cloud service user, you can specify the user to be the Current account or Other account.
If you select Other account, enter the account ID, which is the Domain ID on the My Credential page.
+ - Include or Exclude
- Cloud service user, Federated user
|
@@ -65,7 +65,7 @@ This topic describes how to configure a custom bucket policy in common mode \(GU
**Figure 2** Parameter settings of a custom bucket policy in the customized mode
- [Table 2](#table25824246144542) lists the meaning of each field.
+ [Table 2](#table25824246144542) lists the meaning of each parameter.
**Table 2** Parameters in bucket policies
@@ -80,7 +80,7 @@ This topic describes how to configure a custom bucket policy in common mode \(GU
Effect
|
- Allow or Deny
+ | Allow or Deny
|
Effect of a bucket policy.
- Allow: Indicates access requests are allowed, if they match the configurations of this bucket policy.
- Deny: Indicates access requests are denied, if they match the configurations of this bucket policy.
@@ -88,7 +88,7 @@ This topic describes how to configure a custom bucket policy in common mode \(GU
|
Principal
|
- - Include or Exclude
- Cloud service user, Federated user
- If you select Cloud service user, you can specify the user to be the Current account or Other account.
If you select Other account, enter the account ID, which is the Domain ID on the My Credential page.
+ - Include or Exclude
- Cloud service user, Federated user
|
@@ -98,7 +98,7 @@ This topic describes how to configure a custom bucket policy in common mode \(GU
|
Resources
|
- - Include or Exclude
- Input format:
Object: object name
+ - Include or Exclude
- Resource input format:
Object: object name
Object set: object name prefix*, *object name suffix, or *
Blank: Indicates that the resource is the entire bucket.
diff --git a/doc/source/obs/user-guide/configuring-a-lifecycle-rule-(browser).md b/doc/source/obs/user-guide/configuring-a-lifecycle-rule-(browser).md
index d5fea526..ede44d62 100644
--- a/doc/source/obs/user-guide/configuring-a-lifecycle-rule-(browser).md
+++ b/doc/source/obs/user-guide/configuring-a-lifecycle-rule-(browser).md
@@ -13,7 +13,7 @@ You can configure a lifecycle management rule for a bucket, and applicable objec
4. Configure a lifecycle rule.
- Configure the basic information.
+ **Basic Information**:
- **Status**:
@@ -27,22 +27,21 @@ You can configure a lifecycle management rule for a bucket, and applicable objec
- **Object name prefix**: Objects that have the specified prefix will be managed by the lifecycle rule. The prefix cannot start with a slash \(/\), cannot have consecutive slashes \(/\), and cannot contain the following special characters: **\\:\*?"<\>|**
- **Bucket**: All objects in the bucket will be managed by the lifecycle rule.
- > **NOTE:**
- >- When **Object name prefix** is selected and the specified prefix and the prefix of an existing lifecycle rule overlap, OBS regards the two rules as one and disables the one to be configured. For example, if a rule with prefix **abc** exists in the system, another rule whose prefix starts with **abc** cannot be configured.
- >- If a lifecycle rule whose **Applies To** is set to **Object name prefix** has been configured, you cannot configure a lifecycle rule whose **Applies To** is set to **Bucket**.
- >- If a lifecycle rule has been configured for the entire bucket, no more rules apply to object name prefix can be added.
+ > **NOTE:**
+ >- When **Object name prefix** is selected and the specified prefix and the prefix of an existing lifecycle rule overlap, OBS regards the two rules as one and disables the one to be configured. For example, if a rule with prefix **abc** exists in the system, another rule whose prefix starts with **abc** cannot be configured.
+ >- If a lifecycle rule whose **Applies To** is set to **Object name prefix** has been configured, you cannot configure a lifecycle rule whose **Applies To** is set to **Bucket**.
+ >- If a lifecycle rule has been configured for the entire bucket, no more rules that apply to object name prefix can be added.
**Current Version** or **Historical Version**:
+ > **NOTE:**
+ >- **Current Version** and **Historical Version** are two concepts for **Versioning**. If **Versioning** is enabled, uploading objects with the same name to the same path generates different versions. The object uploaded lastly is called **Current Version**, and the object uploaded earlier is called **Historical Version**.
+ >- You can configure either, both, or neither of the versions.
+
- **Transition to Warm**: You can specify the number of days after which objects that have been last updated and meet specified conditions are automatically transitioned to **Warm**. This number must be at least 30.
- **Transition to Cold**: You can specify the number of days after which objects that have been last updated and meet specified conditions are automatically transitioned to **Cold**. If objects are configured to be transitioned to both **Warm** and **Cold**, the number of days for transition to **Cold** must be at least 30 days later than that for transition to **Warm**. If only transition to Cold is enabled and transition to **Warm** is disabled, there is no limit on the number of days for transition.
- Deleted upon expiration: You can specify the number of days after which objects that have been last updated and meet the specified conditions are automatically deleted. The expiration time must be greater than the two transition times.
- > **NOTE:**
- >- **Current Version** and **Historical Version** are two concepts for **Versioning**. If **Versioning** is enabled, uploading objects with the same name to the same path generates different versions. The object uploaded lastly is called **Current Version**, and the object uploaded earlier is called **Historical Version**.
- >- You can configure either, both, or neither of the versions.
-
-
For example, the following files are stored in OBS on January 7, 2015:
- log/test1.log
@@ -61,8 +60,8 @@ You can configure a lifecycle management rule for a bucket, and applicable objec
On the current day, if you set the objects with the name prefix **log** to be transitioned to **Warm** 30 days later, transitioned to **Cold** 60 days later, and deleted 100 days later, then OBS will transition **log/clientlog.log**, **log/serverlog.log**, **log/test1.log**, and **log/test2.log** to **Warm** on the 31st day, transition them to **Cold** the 61st day, and delete them on the 101st day.
- > **NOTE:**
- >The storage class transition and deletion of an object may be delayed after the time condition is met. Generally, the delay does not exceed 48 hours.
+ > **NOTE:**
+ >The storage class transition and deletion of an object may be delayed after the time condition is met. Generally, the delay does not exceed 48 hours. If you change the configurations of an existing lifecycle rule, the effective time of the lifecycle rule will change according to the new configurations.
5. Click **Save**.
6. In the **Create Lifecycle Rule** dialog box, click **Save**.
diff --git a/doc/source/obs/user-guide/configuring-a-lifecycle-rule-(console).md b/doc/source/obs/user-guide/configuring-a-lifecycle-rule-(console).md
index cb3d9f6a..008ac527 100644
--- a/doc/source/obs/user-guide/configuring-a-lifecycle-rule-(console).md
+++ b/doc/source/obs/user-guide/configuring-a-lifecycle-rule-(console).md
@@ -4,7 +4,7 @@ You can configure the lifecycle rule for a bucket or an object. You can transiti
## Procedure
-1. In the bucket list, click the bucket to be operated. The **Summary** page of the bucket is displayed.
+1. In the bucket list, click the bucket to be operated. The **Overview** page of the bucket is displayed.
2. In the **Basic Configurations** area, click the **Lifecycle Rules** label. The **Lifecycle Rules** page is displayed.
Alternatively, you can choose **Basic Configurations** \> **Lifecycle Rules** in the navigation pane on the left.
@@ -16,7 +16,7 @@ You can configure the lifecycle rule for a bucket or an object. You can transiti
4. Configure a lifecycle rule.
- Configure the basic information.
+ **Basic Information**:
- **Status**:
@@ -30,22 +30,21 @@ You can configure the lifecycle rule for a bucket or an object. You can transiti
- **Object name prefix**: Objects that have the specified prefix will be managed by the lifecycle rule. The prefix cannot start with a slash \(/\), cannot have consecutive slashes \(/\), and cannot contain the following special characters: **\\:\*?"<\>|**
- **Bucket**: All objects in the bucket will be managed by the lifecycle rule.
- > **NOTE:**
- >- When **Object name prefix** is selected and the specified prefix and the prefix of an existing lifecycle rule overlap, OBS regards the two rules as one and disables the one to be configured. For example, if a rule with prefix **abc** exists in the system, another rule whose prefix starts with **abc** cannot be configured.
- >- If a lifecycle rule whose **Applies To** is set to **Object name prefix** has been configured, you cannot configure a lifecycle rule whose **Applies To** is set to **Bucket**.
- >- If a lifecycle rule has been configured for the entire bucket, no more rules apply to object name prefix can be added.
+ > **NOTE:**
+ >- When **Object name prefix** is selected and the specified prefix and the prefix of an existing lifecycle rule overlap, OBS regards the two rules as one and disables the one to be configured. For example, if a rule with prefix **abc** exists in the system, another rule whose prefix starts with **abc** cannot be configured.
+ >- If a lifecycle rule whose **Applies To** is set to **Object name prefix** has been configured, you cannot configure a lifecycle rule whose **Applies To** is set to **Bucket**.
+ >- If a lifecycle rule has been configured for the entire bucket, no more rules that apply to object name prefix can be added.
**Current Version** or **Historical Version**:
+ > **NOTE:**
+ >- **Current Version** and **Historical Version** are two concepts for **Versioning**. If **Versioning** is enabled, uploading objects with the same name to the same path generates different versions. The object uploaded lastly is called **Current Version**, and the object uploaded earlier is called **Historical Version**.
+ >- You can configure either, both, or neither of the versions.
+
- **Transition to Warm**: You can specify the number of days after which objects that have been last updated and meet specified conditions are automatically transitioned to **Warm**. This number must be at least 30.
- **Transition to Cold**: You can specify the number of days after which objects that have been last updated and meet specified conditions are automatically transitioned to **Cold**. If objects are configured to be transitioned to both **Warm** and **Cold**, the number of days for transition to **Cold** must be at least 30 days later than that for transition to **Warm**. If only transition to Cold is enabled and transition to **Warm** is disabled, there is no limit on the number of days for transition.
- Deleted upon expiration: You can specify the number of days after which objects that have been last updated and meet the specified conditions are automatically deleted. The expiration time must be greater than the two transition times.
- > **NOTE:**
- >- **Current Version** and **Historical Version** are two concepts for **Versioning**. If **Versioning** is enabled, uploading objects with the same name to the same path generates different versions. The object uploaded lastly is called **Current Version**, and the object uploaded earlier is called **Historical Version**.
- >- You can configure either, both, or neither of the versions.
-
-
For example, the following files are stored in OBS on January 7, 2015:
- log/test1.log
@@ -64,8 +63,8 @@ You can configure the lifecycle rule for a bucket or an object. You can transiti
On the current day, if you set the objects with the name prefix **log** to be transitioned to **Warm** 30 days later, transitioned to **Cold** 60 days later, and deleted 100 days later, then OBS will transition **log/clientlog.log**, **log/serverlog.log**, **log/test1.log**, and **log/test2.log** to **Warm** on the 31st day, transition them to **Cold** the 61st day, and delete them on the 101st day.
- > **NOTE:**
- >The storage class transition and deletion of an object may be delayed after the time condition is met. Generally, the delay does not exceed 48 hours.
+ > **NOTE:**
+ >The storage class transition and deletion of an object may be delayed after the time condition is met. Generally, the delay does not exceed 48 hours. If you change the configurations of an existing lifecycle rule, the effective time of the lifecycle rule will change according to the new configurations.
5. Click **OK** to complete the lifecycle rule configuration.
@@ -73,5 +72,5 @@ You can configure the lifecycle rule for a bucket or an object. You can transiti
You can click **Edit** under the **Operation** column of a lifecycle rule, to edit the rule. Also you can click **Disable** or **Enable** to disable or enable it.
-If you want to delete more than one lifecycle rules at a time, select them and click **Delete** above the list.
+If you want to delete more than one lifecycle rule at a time, select them and click **Delete** above the list.
diff --git a/doc/source/obs/user-guide/configuring-a-standard-bucket-policy.md b/doc/source/obs/user-guide/configuring-a-standard-bucket-policy.md
index e673cdfa..70e465ce 100644
--- a/doc/source/obs/user-guide/configuring-a-standard-bucket-policy.md
+++ b/doc/source/obs/user-guide/configuring-a-standard-bucket-policy.md
@@ -4,7 +4,7 @@ For standard bucket policy, OBS offers three options, namely the Private, Public
## Procedure
-1. In the bucket list, click the bucket to be operated. The **Summary** page of the bucket is displayed.
+1. In the bucket list, click the bucket to be operated. The **Overview** page of the bucket is displayed.
2. In the navigation pane on the left, click **Permissions** to go to the permission management page.
3. On the **Bucket Policies** tab page, select a policy from the **Standard Bucket Policies** area.
@@ -12,8 +12,8 @@ For standard bucket policy, OBS offers three options, namely the Private, Public
- **Public Read**: Any user can read objects in the bucket.
- **Public Read and Write**: Any user can read, write, and delete objects in the bucket.
- > **NOTE:**
- >For your data security, the **Public Read** and **Public Read and Write** policies are not recommended.
+ > **NOTE:**
+ >For your data security, the **Public Read** and **Public Read and Write** policies are not recommended.
**Figure 1** Standard bucket policies
diff --git a/doc/source/obs/user-guide/configuring-access-logging-for-a-bucket.md b/doc/source/obs/user-guide/configuring-access-logging-for-a-bucket.md
index d91db10b..15cbe1e5 100644
--- a/doc/source/obs/user-guide/configuring-access-logging-for-a-bucket.md
+++ b/doc/source/obs/user-guide/configuring-access-logging-for-a-bucket.md
@@ -11,7 +11,7 @@ After logging is enabled for a bucket, OBS automatically converts bucket logs in
**Figure 1** Logging
-4. Select a bucket from existing buckets to save log files. Log delivery users of the selected bucket will be automatically assigned with the permission to read the bucket ACL and write logs to the bucket.
+4. Select an existing bucket where you want to store log files. Log delivery users of the selected bucket will be automatically assigned with the permission to read the bucket ACL and write logs to the bucket.
5. Enter a prefix for the **Log File Name Prefix**.
After logging is enabled, generated logs are named in the following format:
@@ -29,9 +29,10 @@ After logging is enabled for a bucket, OBS automatically converts bucket logs in
- If the bucket named **bucket** is selected to save log files, and the log file name prefix is set to **bucket-log/**, all log files delivered to the bucket are saved in the **bucket-log** folder. A log file is named as follows: **2015-06-29-12-22-07-N7MXLAF1BDG7MPDV**.
- If the bucket named **bucket** is selected to save log files, and the log file name prefix is set to **bucket-log**, then no folder is created for log files delivered to the bucket. A log file is named as follows: **bucket-log2015-06-29-12-22-07-N7MXLAF1BDG7MPDV**.
+6. Click **OK**.
+
After logging is configured, you can view operation logs in the bucket that stores the logs in approximately fifteen minutes.
-6. Click **OK**.
## Follow-up Procedure
diff --git a/doc/source/obs/user-guide/configuring-an-object-acl.md b/doc/source/obs/user-guide/configuring-an-object-acl.md
index 600d6da7..9d7164eb 100644
--- a/doc/source/obs/user-guide/configuring-an-object-acl.md
+++ b/doc/source/obs/user-guide/configuring-an-object-acl.md
@@ -5,9 +5,9 @@
1. In the bucket list, click the bucket to be operated. The **Overview** page of the bucket is displayed.
2. In the navigation pane on the left, click **Objects**.
3. Click the object to be operated.
-4. On the **Object ACL** tab, click **Edit** to set ACL permissions of the **Owner**, **Anonymous User**, and **Registered User** for the target object.
+4. On the **Object ACL** tab, click **Edit** to set ACL permissions of the **Owner**, **Registered User**, and **Anonymous User** for the target object.
- > **NOTE:**
+ > **NOTE:**
>If the object is encrypted, the ACL permission cannot be configured for registered users and anonymous users.
5. **Optional**: Click **Add**. For details, see [Figure 1](#fig3474335195326).
diff --git a/doc/source/obs/user-guide/configuring-an-object-policy.md b/doc/source/obs/user-guide/configuring-an-object-policy.md
index 03a1d48f..b0c98d89 100644
--- a/doc/source/obs/user-guide/configuring-an-object-policy.md
+++ b/doc/source/obs/user-guide/configuring-an-object-policy.md
@@ -4,7 +4,7 @@ An object policy applies to a specific object, which is also part of a bucket po
## Procedure
-1. In the bucket list, click the bucket to be operated. The **Summary** page of the bucket is displayed.
+1. In the bucket list, click the bucket to be operated. The **Overview** page of the bucket is displayed.
2. In the navigation pane on the left, click **Objects**.
3. On the right of the object to be operated, choose **More** \> **Configure Object Policy**. The **Configure Object Policy** dialog box is displayed.
4. Select a proper policy mode as required. Valid options are as follows:
@@ -13,8 +13,8 @@ An object policy applies to a specific object, which is also part of a bucket po
- Read and write mode: The authorized user has the read and write permissions to the object. For follow-up procedure, see [5](#li3552175452220).
- Customized: The authorized user will be granted with customized permissions to the object. For detailed configuration, see [6](#li588503161565).
- > **NOTE:**
- >You can configure only one object policy at a time.
+ > **NOTE:**
+ >You can configure only one object policy at a time.
5. For read-only and read and write modes, enter information about the authorized user in the following format and click **OK**.
diff --git a/doc/source/obs/user-guide/configuring-cors-(browser).md b/doc/source/obs/user-guide/configuring-cors-(browser).md
index c2b7387f..33edccf7 100644
--- a/doc/source/obs/user-guide/configuring-cors-(browser).md
+++ b/doc/source/obs/user-guide/configuring-cors-(browser).md
@@ -8,8 +8,8 @@ This section describes how to use CORS in HTML5 to implement cross-origin access
2. Select the bucket to be configured and click **More** \> **Configure CORS Rule**.
3. Click **Add**.
- > **NOTE:**
- >You can set a maximum of 100 CORS rules for one bucket.
+ > **NOTE:**
+ >You can set a maximum of 100 CORS rules for one bucket.
4. In the **Add CORS Rule** dialog box that is displayed, enter CORS rules.
@@ -43,7 +43,7 @@ This section describes how to use CORS in HTML5 to implement cross-origin access
| Allowed Header
|
Specifies the allowed header of cross-origin requests. This parameter is optional. Only CORS requests matching the allowed header are valid.
- You can enter multiple allowed headers (one per line) and each line can contain one wildcard character (*) at most. Spaces and special characters including &:< are not allowed.
+ You can enter multiple allowed headers (one per line) and each line can contain one wildcard character (*) at most. Spaces and special characters including &:< are not allowed.
|
Exposed Header
@@ -54,7 +54,7 @@ This section describes how to use CORS in HTML5 to implement cross-origin access
|
Cache Duration (s)
|
- Mandatory; specifies the duration that your browser can cache CORS responses, expressed in seconds. The default value is 100.
+ | Mandatory. Specifies the duration that your browser can cache CORS responses, expressed in seconds. The default value is 100.
|
|
@@ -63,7 +63,7 @@ This section describes how to use CORS in HTML5 to implement cross-origin access
5. Click **OK**.
6. Click **OK** to save the rules.
- After CORS is successfully configured, only the addresses specified in **Allowed Origin** can access a bucket on OBS using the method specified in **Allowed Method**. For example, you configure CORS parameters of bucket **testbucket** as follows: **Allowed Origin: www.example.com**; **Allowed Method: GET**; **Allowed Header**: left blank; **Exposed Header**: left blank; **Cache Duration \(s\): 100**
+ After CORS is successfully configured, only the addresses specified in **Allowed Origin** can access a bucket in OBS using the method specified in **Allowed Method**. For example, you configure CORS parameters of bucket **testbucket** as follows: **Allowed Origin: www.example.com**; **Allowed Method: GET**; **Allowed Header**: left blank; **Exposed Header**: left blank; **Cache Duration \(s\): 100**. Then OBS only allows GET requests from **www.example.com** to access the **testbucket**, without restrictions on request headers. The client can cache the CORS response for 100 seconds.
7. In the displayed dialog box, click **Close** to close the dialog box.
diff --git a/doc/source/obs/user-guide/configuring-cors.md b/doc/source/obs/user-guide/configuring-cors.md
index cb46e56b..e68875a0 100644
--- a/doc/source/obs/user-guide/configuring-cors.md
+++ b/doc/source/obs/user-guide/configuring-cors.md
@@ -8,15 +8,15 @@ Static website hosting has been configured. For details about how to configure s
## Procedure
-1. In the bucket list, click the bucket to be operated. The **Summary** page of the bucket is displayed.
-2. In the **Basic Configurations** area, click the **CORS Rules** label. The **CORS Rules** page is displayed.
+1. In the bucket list, click the bucket to be operated. The **Overview** page of the bucket is displayed.
+2. In the **Basic Configurations** area, click the **CORS Rules**. The **CORS Rules** page is displayed.
Alternatively, you can choose **Basic Configurations** \> **CORS Rules** in the navigation pane on the left.
3. Click **Create**. The **Create CORS Rule** dialog box is displayed. See [Figure 1](#fig2425430173411) for details.
- > **NOTE:**
- >You can set a maximum of 100 CORS rules for one bucket.
+ > **NOTE:**
+ >You can set a maximum of 100 CORS rules for one bucket.
**Figure 1** Creating a CORS rule
diff --git a/doc/source/obs/user-guide/configuring-logging.md b/doc/source/obs/user-guide/configuring-logging.md
index 20bae497..cba5af6f 100644
--- a/doc/source/obs/user-guide/configuring-logging.md
+++ b/doc/source/obs/user-guide/configuring-logging.md
@@ -15,7 +15,7 @@ The log delivery user group has been assigned the **Write** and **ACL View**
**Figure 1** Logging
-4. Select a bucket from existing buckets to save log files. Log delivery users of the selected bucket will be automatically assigned with the permission to read the bucket ACL and write logs to the bucket.
+4. Select an existing bucket where you want to store log files. Log delivery users of the selected bucket will be automatically assigned with the permission to read the bucket ACL and write logs to the bucket.
5. Enter a prefix for the **Log File Name Prefix**.
After logging is enabled, generated logs are named in the following format:
@@ -33,8 +33,6 @@ The log delivery user group has been assigned the **Write** and **ACL View**
- If the bucket named **bucket** is selected to save log files, and the log file name prefix is set to **bucket-log/**, all log files delivered to the bucket are saved in the **bucket-log** folder. A log file is named as follows: **2015-06-29-12-22-07-N7MXLAF1BDG7MPDV**.
- If the bucket named **bucket** is selected to save log files, and the log file name prefix is set to **bucket-log**, then no folder is created for log files delivered to the bucket. A log file is named as follows: **bucket-log2015-06-29-12-22-07-N7MXLAF1BDG7MPDV**.
- After logging is configured, you can view operation logs in the bucket that stores the logs in approximately fifteen minutes.
-
6. Click **OK**.
7. In the displayed dialog box, click **Close** to close the dialog box.
diff --git a/doc/source/obs/user-guide/configuring-redirection.md b/doc/source/obs/user-guide/configuring-redirection.md
index d6ce484c..ffbf93fc 100644
--- a/doc/source/obs/user-guide/configuring-redirection.md
+++ b/doc/source/obs/user-guide/configuring-redirection.md
@@ -6,14 +6,14 @@ You can configure static website hosting by redirecting all requests for a bucke
Web page files of the static website have been uploaded to a bucket.
-If the web page files are in the Cold storage class, restored them first. For more information, see [Restoring a Cold File Stored in OBS](restoring-a-cold-file-stored-in-obs.md).
+If the web page files are in the Cold storage class, restore them first. For more information, see [Restoring a Cold File Stored in OBS](restoring-a-cold-file-stored-in-obs.md).
-> **NOTICE:**
->If the hosted static website needs to be accessed by anyone, authorize anonymous users the permission to access static website files in the bucket. The configuration of static website hosting takes effect within two minutes after the configuration.
+> **NOTICE:**
+>If the hosted static website needs to be accessed by anyone, authorize anonymous users the permission to access static website files in the bucket. The configuration of static website hosting takes effect within two minutes after the configuration.
## Procedure
-1. In the bucket list, click the bucket to be operated. The **Summary** page of the bucket is displayed.
+1. In the bucket list, click the bucket to be operated. The **Overview** page of the bucket is displayed.
2. In the **Basic Configurations** area, click the **Static Website Hosting** label. The **Static Website Hosting** page is displayed.
Alternatively, you can choose **Basic Configurations** \> **Static Website Hosting** from the navigation pane on the left.
@@ -42,7 +42,7 @@ If the web page files are in the Cold storage class, restored them first. For mo
9. **Verification**: Input the access domain name of the bucket in the web browser and press **Enter**. The bucket or URL to which requests are redirected will be displayed.
- > **NOTE:**
- >In some conditions, you may need to clear the browser cache before the expected results are displayed.
+ > **NOTE:**
+ >In some conditions, you may need to clear the browser cache before the expected results are displayed.
diff --git a/doc/source/obs/user-guide/configuring-static-website-hosting.md b/doc/source/obs/user-guide/configuring-static-website-hosting.md
index 43625f80..8eee7b1a 100644
--- a/doc/source/obs/user-guide/configuring-static-website-hosting.md
+++ b/doc/source/obs/user-guide/configuring-static-website-hosting.md
@@ -6,14 +6,14 @@ This section describes how to configure static website hosting for buckets and u
Web page files of the static website have been uploaded to a bucket.
-If the web page files are in the Cold storage class, restored them first. For more information, see [Restoring a Cold File Stored in OBS](restoring-a-cold-file-stored-in-obs.md).
+If the web page files are in the Cold storage class, restore them first. For more information, see [Restoring a Cold File Stored in OBS](restoring-a-cold-file-stored-in-obs.md).
-> **NOTICE:**
->If the hosted static website needs to be accessed by anyone, authorize anonymous users the permission to access static website files in the bucket. The configuration of static website hosting takes effect within two minutes after the configuration.
+> **NOTICE:**
+>If the hosted static website needs to be accessed by anyone, authorize anonymous users the permission to access static website files in the bucket. The configuration of static website hosting takes effect within two minutes after the configuration.
## Procedure
-1. In the bucket list, click the bucket to be operated. The **Summary** page of the bucket is displayed.
+1. In the bucket list, click the bucket to be operated. The **Overview** page of the bucket is displayed.
2. **Optional**: To ensure that a hosted static website can be accessed by all users, configure the object ACL or bucket policy as follows, so that all static website files in the bucket can be accessed publicly.
Authorize anonymous users the permission to read files on the static website. For details, see [Authorizing Access Permissions to Anonymous Users](authorizing-access-permissions-to-anonymous-users.md).
@@ -40,11 +40,11 @@ If the web page files are in the Cold storage class, restored them first. For mo
7. Set the values of **Home Page** and **404 Error Page**.
- - **Home Page**: specifies the default homepage of the static website. When OBS Console is used to configure static website hosting, only HTML web pages are supported. When SDKs are used to configure static website hosting, OBS does not have such a restriction but the **Content-Type** of objects must be specified.
+ - **Home Page**: specifies the default homepage of the static website. When OBS Console is used to configure static website hosting, only HTML web pages are supported. When are used to configure static website hosting, OBS does not have such a restriction but the **Content-Type** of objects must be specified.
OBS only allows files such as **index.html** in the root directory of a bucket to function as the default homepage. That is to say, do not set the default homepage with a multi-level directory structure \(for example, **/page/index.html**\).
- - **404 Error Page**: specifies the error page returned when an error occurs during static website access. When OBS Console is used to configure static website hosting, only HTML, JPG, PNG, BMP, and WEBP files under the root directory are supported. When APIs or SDKs are used to configure static website hosting, OBS does not have such a restriction but the **Content-Type** of objects must be specified.
+ - **404 Error Page**: specifies the error page returned when an error occurs during static website access. When OBS Console is used to configure static website hosting, only HTML, JPG, PNG, BMP, and WEBP files under the root directory are supported. When APIs are used to configure static website hosting, OBS does not have such a restriction but the **Content-Type** of objects must be specified.
8. **Optional**: In **Redirection Rules**, configure redirection rules. Requests that comply with the redirection rules are redirected to the specific host or page.
@@ -65,7 +65,7 @@ If the web page files are in the Cold storage class, restored them first. For mo
|
KeyPrefixEquals
|
- Object name prefix on which the redirection rule takes effect When a request is sent for accessing an object, the redirection rule takes effect if the object name prefix matches the value specified for this parameter.
+ | Object name prefix on which the redirection rule takes effect. When a request is sent for accessing an object, the redirection rule takes effect if the object name prefix matches the value specified for this parameter.
For example, to redirect the request for object ExamplePage.html, set the KeyPrefixEquals to ExamplePage.html.
|
@@ -84,7 +84,7 @@ If the web page files are in the Cold storage class, restored them first. For mo