From c90e4a4dc0325f5415b42efa34f6d54b18f79ae1 Mon Sep 17 00:00:00 2001 From: Maksim Ryndin Date: Fri, 7 Jun 2024 06:23:21 +0000 Subject: [PATCH] update readme --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 7af9bd2..4afaa76 100644 --- a/README.md +++ b/README.md @@ -26,9 +26,9 @@ To use buf workspaces, simply call `tonic_buf_build::compile_from_buf_workspace` For complete and working examples, take a look at the examples folder. -When the buf files are not located not in the current directory, you can configure the *absolute* path to the directory, containing either `buf.yaml` or `buf.work.yaml`, and call the corresponding `tonic_buf_build::compile_from_buf_with_config` or `tonic_buf_build::compile_from_buf_workspace_with_config`. +When the buf files are not located in the current directory, you can configure the *absolute* path to the directory, containing either `buf.yaml` or `buf.work.yaml`, and call the corresponding `tonic_buf_build::compile_from_buf_with_config` or `tonic_buf_build::compile_from_buf_workspace_with_config`. -Consider the following build.rs where the workspace directory is located one level above the crate (a usual case for multilanguage clients with common protos) +Consider the following build.rs where the buf workspace directory is located one level above the crate (a usual case for multilanguage clients with common protos) ```rust use std::env;