From 649399e29e369cb5117e5658c096d157e07f4d76 Mon Sep 17 00:00:00 2001 From: shiyu22 Date: Tue, 26 Oct 2021 14:31:03 +0800 Subject: [PATCH] [skip ci]Update development.md (#10544) Signed-off-by: shiyu22 --- DEVELOPMENT.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/DEVELOPMENT.md b/DEVELOPMENT.md index 8a0ef62c91..00ddfd5d82 100644 --- a/DEVELOPMENT.md +++ b/DEVELOPMENT.md @@ -120,7 +120,7 @@ Note: go1.15 is required to build Milvus. #### Docker & Docker Compose -Milvus depends on etcd, Pulsar and MinIO. Using Docker Compose to manage these is an easy way in a local development. To install Docker and Docker Compose in your development environment, follow the instructions from the Docker website below: +Milvus depends on etcd, Pulsar and MinIO. Using Docker Compose to manage these is an easy way in local development. To install Docker and Docker Compose in your development environment, follow the instructions from the Docker website below: - Docker: https://docs.docker.com/get-docker/ - Docker Compose: https://docs.docker.com/compose/install/ @@ -135,7 +135,7 @@ $ make all If this command succeed, you will now have an executable at `bin/milvus` off of your Milvus project directory. -If you want to update proto file before make, we can use the following command: +If you want to update proto file before `make`, we can use the following command: ```shell $ make generated-proto-go ``` @@ -219,7 +219,7 @@ $ make codecov-cpp ### E2E Tests -Milvus uses Python SDK to write test cases to verify the correctness of Milvus functions. Before run E2E tests, you need a running Milvus: +Milvus uses Python SDK to write test cases to verify the correctness of Milvus functions. Before running E2E tests, you need a running Milvus: ```shell # Running Milvus cluster @@ -235,7 +235,7 @@ $ cd ../../../ $ ./scripts/start_standalone.sh ``` -To run E2E tests, use these command: +To run E2E tests, use these commands: ```shell $ cd tests/python_client