From f0ed1aba14ff53e356343178d5634af5e624a3f6 Mon Sep 17 00:00:00 2001
From: Martin <1224973+mavaa@users.noreply.github.com>
Date: Wed, 12 Aug 2020 16:51:42 +0200
Subject: [PATCH] Fix incorrectly named grpc-tools flag

Was  "--generate_package_definitions" (with an s) but should be "generate_package_definition" as in the documentation here: https://github.com/grpc/grpc-node/tree/master/packages/grpc-tools
---
 packages/grpc-js/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/grpc-js/README.md b/packages/grpc-js/README.md
index 4d0cb548..dadcd188 100644
--- a/packages/grpc-js/README.md
+++ b/packages/grpc-js/README.md
@@ -28,7 +28,7 @@ This library does not directly handle `.proto` files. To use `.proto` files with
 `@grpc/grpc-js` is almost a drop-in replacement for `grpc`, but you may need to make a few code changes to use it:
 
 - If you are currently loading `.proto` files using `grpc.load`, that function is not available in this library. You should instead load your `.proto` files using `@grpc/proto-loader` and load the resulting package definition objects into `@grpc/grpc-js` using `grpc.loadPackageDefinition`.
-- If you are currently loading packages generated by `grpc-tools`, you should instead generate your files using the `--generate_package_definitions` option in `grpc-tools`, then load the object exported by the generated file into `@grpc/grpc-js` using `grpc.loadPackageDefinition`.
+- If you are currently loading packages generated by `grpc-tools`, you should instead generate your files using the `generate_package_definition` option in `grpc-tools`, then load the object exported by the generated file into `@grpc/grpc-js` using `grpc.loadPackageDefinition`.
 - If you have a server and you are using `Server#bind` to bind ports, you will need to use `Server#bindAsync` instead.
 
 ## Some Notes on API Guarantees