[skip e2e]Update milvus component name (#14161)

Signed-off-by: yanliang567 <yanliang.qiao@zilliz.com>

docs/design_docs/root_coordinator_recovery_on_power_failure.md

@@ -35,7 +35,7 @@
 1. In the processing of `create index`, `RootCoord` calls `metaTable`'s `GetNotIndexedSegments` to get all segment ids that are not indexed.
 2. After getting the segment ids, `RootCoord` calls `IndexCoord` to create index on these segment ids.
 3. In the current implementation, the `create index` requests will return after the segment ids are put into a go channel.
-4. The `RC` starts a background task that keeps reading the segment ids from the go channel, and then calls the `IndexCoord` to create the index.
+4. The `RootCoord` starts a background task that keeps reading the segment ids from the go channel, and then calls the `IndexCoord` to create the index.
 5. There is a fault here, the segment ids have been put into the go channel in the processing function of the grpc request, and then the grpc returns, but the `RootCoord`'s background task has not yet read them from the go channel, then `RootCoord` crashes. At this time, the client thinks that the index is created, but the `RootCoord` does not call `IndexCoord` to create the index.
 6. The solution for the fault mentioned in item 5:
    - Remove the go channel and `RootCoord`'s background task.