milvus-io
/
milvus
mirror of https://github.com/milvus-io/milvus.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

[skip ci]Fix word and grammar errors (#11489) 

Signed-off-by: zilliz <zilliz@zillizdeMacBook-Pro.local>

Co-authored-by: zilliz <zilliz@zillizdeMacBook-Pro.local>
pull/11520/head
jingkl 2021-11-09 19:05:57 +08:00 committed by GitHub
parent dd34a0d3ad
commit 1db21bee96
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/design_docs/MEP-Template.md
View File

@ -23,7 +23,7 @@ Briefly list any new interfaces that will be introduced as part of this proposal
## Design Details(required)
Describe the new thing you want to do in appropriate detail. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences. Use judgement based on the scope of the change.
Describe the new thing you want to do appropriate detail. This may be fairly extensive and have large subsections of its own. Or it may be a few sentences. Use judgment based on the scope of the change.
## Compatibility, Deprecation, and Migration Plan(optional)
- What impact (if any) will there be on existing users?
@ -34,7 +34,7 @@ Describe the new thing you want to do in appropriate detail. This may be fairly
## Test Plan(required)
Describe in a few sentences how the MEP will be tested. We are mostly interested in system tests (since unit-tests are specific to implementation details). How will we know that the implementation works as expected? How will we know nothing broke?
Describe in a few sentences how the MEP will be tested. We are mostly interested in system tests (since unit tests are specific to implementation details). How will we know that the implementation works as expected? How will we know nothing broke?
## Rejected Alternatives(optional)