Update content

umn/source/faqs/index.rst

@@ -23,6 +23,6 @@ FAQs
    redis_commands/index
    instance_scaling_and_upgrade/index
    monitoring_and_alarm/index
-   data_backup_export_and_migration/index
+   data_backup,_export,_and_migration/index
    analysis_of_big_keys_and_hot_keys/index
    master_standby_switchover/index

umn/source/faqs/instance_scaling_and_upgrade/index.rst

@@ -15,7 +15,7 @@ Instance Scaling and Upgrade
    :maxdepth: 1
    :hidden: 
 
-   can_dcs_redis_instances_be_upgraded_for_example_from_redis_3.0_to_redis_4.0_or_5.0
+   can_dcs_redis_instances_be_upgraded,_for_example,_from_redis_3.0_to_redis_4.0_or_5.0
    are_services_interrupted_if_maintenance_is_performed_during_the_maintenance_time_window
    are_instance_resources_affected_during_specification_modification
    are_services_interrupted_during_specification_modification

umn/source/faqs/monitoring_and_alarm/index.rst

@@ -21,6 +21,6 @@ Monitoring and Alarm
    does_redis_support_command_audits
    what_should_i_do_if_the_monitoring_data_of_a_dcs_redis_instance_is_abnormal
    why_is_used_memory_greater_than_available_memory
-   why_does_bandwidth_usage_exceed_100pct
+   why_does_bandwidth_usage_exceed_100%
    why_is_the_rejected_connections_metric_displayed
    why_is_flow_control_triggered_how_do_i_handle_it

umn/source/faqs/redis_usage/index.rst

@@ -33,7 +33,7 @@ Redis Usage
    :maxdepth: 1
    :hidden: 
 
-   why_is_cpu_usage_of_a_dcs_redis_instance_100pct
+   why_is_cpu_usage_of_a_dcs_redis_instance_100%
    can_i_change_the_vpc_and_subnet_for_a_dcs_redis_instance
    why_arent_security_groups_configured_for_dcs_redis_4.0_and_5.0_instances
    do_dcs_redis_instances_limit_the_size_of_a_key_or_value
@@ -44,7 +44,7 @@ Redis Usage
    does_dcs_for_redis_support_sentinel
    what_is_the_default_data_eviction_policy
    what_should_i_do_if_an_error_occurs_in_redis_exporter
-   why_is_memory_usage_more_than_100pct
+   why_is_memory_usage_more_than_100%
    why_is_redisson_distributed_lock_not_supported_by_dcs_proxy_cluster_redis_3.0_instances
    can_i_customize_or_change_the_port_for_accessing_a_dcs_instance
    can_i_modify_the_connection_addresses_for_accessing_a_dcs_instance

umn/source/getting_started/accessing_an_instance/access_in_different_languages/index.rst

@@ -22,7 +22,7 @@ Access in Different Languages
    lettuce_integration_with_spring_boot
    clients_in_python
    go-redis
-   hiredis_in_c
+   hiredis_in_c++
    csharp
    php/index
    node.js

umn/source/service_overview/accessing_dcs/how_to_access_dcs.rst

@@ -9,7 +9,7 @@ There are two ways to access DCS:
 
 -  Using the management console
 
-   The DCS provides a web-based management console. To launch the DCS console, create an account on the management console and log in, and then choose **Database** > **Distributed Cache Service** on the homepage. On the DCS console, you can create, restart, and delete DCS instances, and change their passwords.
+   The DCS provides a web-based management console. To launch the DCS console, create an account on the management console and log in, and then choose **Application** > **Distributed Cache Service** on the homepage. On the DCS console, you can create, restart, and delete DCS instances, and change their passwords.
 
 -  Using APIs