translation: refine translation of binary_search_tree.md (#1484)

* translation_refine_bst

Signed-off-by: steventimes <stevenyang0316@gmail.com>

* Update binary_search_tree.md

* Update binary_search_tree.md

---------

Signed-off-by: steventimes <stevenyang0316@gmail.com>
Co-authored-by: Yudong Jin <krahets@163.com>

en/docs/chapter_tree/binary_search_tree.md

@@ -9,15 +9,15 @@ As shown in the figure below, a <u>binary search tree</u> satisfies the followin
 
 ## Operations on a binary search tree
 
-We encapsulate the binary search tree as a class `BinarySearchTree` and declare a member variable `root`, pointing to the tree's root node.
+We encapsulate the binary search tree as a class `BinarySearchTree` and declare a member variable `root` pointing to the tree's root node.
 
 ### Searching for a node
 
-Given a target node value `num`, one can search according to the properties of the binary search tree. As shown in the figure below, we declare a node `cur` and start from the binary tree's root node `root`, looping to compare the size relationship between the node value `cur.val` and `num`.
+Given a target node value `num`, one can search according to the properties of the binary search tree. As shown in the figure below, we declare a node `cur`, start from the binary tree's root node `root`, and loop to compare the size between the node value `cur.val` and `num`.
 
 - If `cur.val < num`, it means the target node is in `cur`'s right subtree, thus execute `cur = cur.right`.
 - If `cur.val > num`, it means the target node is in `cur`'s left subtree, thus execute `cur = cur.left`.
-- If `cur.val = num`, it means the target node is found, exit the loop and return the node.
+- If `cur.val = num`, it means the target node is found, exit the loop, and return the node.
 
 === "<1>"
     ![Example of searching for a node in a binary search tree](binary_search_tree.assets/bst_search_step1.png)
@@ -31,7 +31,7 @@ Given a target node value `num`, one can search according to the properties of t
 === "<4>"
     ![bst_search_step4](binary_search_tree.assets/bst_search_step4.png)
 
-The search operation in a binary search tree works on the same principle as the binary search algorithm, eliminating half of the possibilities in each round. The number of loops is at most the height of the binary tree. When the binary tree is balanced, it uses $O(\log n)$ time. Example code is as follows:
+The search operation in a binary search tree works on the same principle as the binary search algorithm, eliminating half of the cases in each round. The number of loops is at most the height of the binary tree. When the binary tree is balanced, it uses $O(\log n)$ time. The example code is as follows:
 
 ```src
 [file]{binary_search_tree}-[class]{binary_search_tree}-[func]{search}
@@ -41,15 +41,15 @@ The search operation in a binary search tree works on the same principle as the
 
 Given an element `num` to be inserted, to maintain the property of the binary search tree "left subtree < root node < right subtree," the insertion operation proceeds as shown in the figure below.
 
-1. **Finding the insertion position**: Similar to the search operation, start from the root node and loop downwards according to the size relationship between the current node value and `num` until passing through the leaf node (traversing to `None`) then exit the loop.
-2. **Insert the node at that position**: Initialize the node `num` and place it where `None` was.
+1. **Finding insertion position**: Similar to the search operation, start from the root node, loop downwards according to the size relationship between the current node value and `num`, until the leaf node is passed (traversed to `None`), then exit the loop.
+2. **Insert the node at this position**: Initialize the node `num` and place it where `None` was.
 
 ![Inserting a node into a binary search tree](binary_search_tree.assets/bst_insert.png)
 
 In the code implementation, note the following two points.
 
-- The binary search tree does not allow duplicate nodes; otherwise, it will violate its definition. Therefore, if the node to be inserted already exists in the tree, the insertion is not performed, and it directly returns.
-- To perform the insertion operation, we need to use the node `pre` to save the node from the last loop. This way, when traversing to `None`, we can get its parent node, thus completing the node insertion operation.
+- The binary search tree does not allow duplicate nodes to exist; otherwise, its definition would be violated. Therefore, if the node to be inserted already exists in the tree, the insertion is not performed, and the node returns directly.
+- To perform the insertion operation, we need to use the node `pre` to save the node from the previous loop. This way, when traversing to `None`, we can get its parent node, thus completing the node insertion operation.
 
 ```src
 [file]{binary_search_tree}-[class]{binary_search_tree}-[func]{insert}
@@ -59,9 +59,9 @@ Similar to searching for a node, inserting a node uses $O(\log n)$ time.
 
 ### Removing a node
 
-First, find the target node in the binary tree, then remove it. Similar to inserting a node, we need to ensure that after the removal operation is completed, the property of the binary search tree "left subtree < root node < right subtree" is still satisfied. Therefore, based on the number of child nodes of the target node, we divide it into 0, 1, and 2 cases, performing the corresponding node removal operations.
+First, find the target node in the binary tree, then remove it. Similar to inserting a node, we need to ensure that after the removal operation is completed, the property of the binary search tree "left subtree < root node < right subtree" is still satisfied. Therefore, based on the number of child nodes of the target node, we divide it into three cases: 0, 1, and 2, and perform the corresponding node removal operations.
 
-As shown in the figure below, when the degree of the node to be removed is $0$, it means the node is a leaf node, and it can be directly removed.
+As shown in the figure below, when the degree of the node to be removed is $0$, it means the node is a leaf node and can be directly removed.
 
 ![Removing a node in a binary search tree (degree 0)](binary_search_tree.assets/bst_remove_case1.png)
 
@@ -96,9 +96,9 @@ The operation of removing a node also uses $O(\log n)$ time, where finding the n
 
 ### In-order traversal is ordered
 
-As shown in the figure below, the in-order traversal of a binary tree follows the "left $\rightarrow$ root $\rightarrow$ right" traversal order, and a binary search tree satisfies the size relationship "left child node $<$ root node $<$ right child node".
+As shown in the figure below, the in-order traversal of a binary tree follows the traversal order of "left $\rightarrow$ root $\rightarrow$ right," and a binary search tree satisfies the size relationship of "left child node $<$ root node $<$ right child node."
 
-This means that in-order traversal in a binary search tree always traverses the next smallest node first, thus deriving an important property: **The in-order traversal sequence of a binary search tree is ascending**.
+This means that when performing in-order traversal in a binary search tree, the next smallest node will always be traversed first, thus leading to an important property: **The sequence of in-order traversal in a binary search tree is ascending**.
 
 Using the ascending property of in-order traversal, obtaining ordered data in a binary search tree requires only $O(n)$ time, without the need for additional sorting operations, which is very efficient.
 
@@ -106,7 +106,7 @@ Using the ascending property of in-order traversal, obtaining ordered data in a
 
 ## Efficiency of binary search trees
 
-Given a set of data, we consider using an array or a binary search tree for storage. Observing the table below, the operations on a binary search tree all have logarithmic time complexity, which is stable and efficient. Only in scenarios of high-frequency addition and low-frequency search and removal, arrays are more efficient than binary search trees.
+Given a set of data, we consider using an array or a binary search tree for storage. Observing the table below, the operations on a binary search tree all have logarithmic time complexity, which is stable and efficient. Arrays are more efficient than binary search trees only in scenarios involving frequent additions and infrequent searches or removals.
 
 <p align="center"> Table <id> &nbsp; Efficiency comparison between arrays and search trees </p>
 
@@ -116,9 +116,9 @@ Given a set of data, we consider using an array or a binary search tree for stor
 | Insert element | $O(1)$         | $O(\log n)$        |
 | Remove element | $O(n)$         | $O(\log n)$        |
 
-In ideal conditions, the binary search tree is "balanced," thus any node can be found within $\log n$ loops.
+Ideally, the binary search tree is "balanced," allowing any node can be found within $\log n$ loops.
 
-However, continuously inserting and removing nodes in a binary search tree may lead to the binary tree degenerating into a chain list as shown in the figure below, at which point the time complexity of various operations also degrades to $O(n)$.
+However, if we continuously insert and remove nodes in a binary search tree, it may degenerate into a linked list as shown in the figure below, where the time complexity of various operations also degrades to $O(n)$.
 
 ![Degradation of a binary search tree](binary_search_tree.assets/bst_degradation.png)