Skip to content

Commit 42c96cf

Browse files
authored
Merge pull request #228 from DinoChiesa/master
clarify a couple things in README
2 parents 3382dd9 + e7c7377 commit 42c96cf

File tree

1 file changed

+4
-6
lines changed

1 file changed

+4
-6
lines changed

README.md

Lines changed: 4 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -9,11 +9,11 @@ This is a tool for administering Apigee Edge things, including
99

1010
This tool and the library included here is not an official Google product.
1111
Support is available on a best-effort basis via github or [the community site](https://www.googlecloudcommunity.com/gc/Apigee/bd-p/cloud-apigee).
12-
Pull requests are welcomed.
12+
Pull requests are welcomed.
1313

1414
## This tool does not support Apigee X or hybrid
1515

16-
This tool works with Apigee Edge. It does not work with Apigee X or hybrid.
16+
This tool works with Apigee Edge. It does not work with Apigee X or hybrid.
1717
For a similar tool that works with X or hybrid, see [here](https://github.com/srinandan/apigeecli).
1818

1919
## Contents
@@ -31,19 +31,17 @@ For a similar tool that works with X or hybrid, see [here](https://github.com/sr
3131

3232
`npm install -g apigeetool`
3333

34-
*NOTE*: The `-g` option places the apigeetool command in your PATH. On "\*nix"-based machines, `sudo` may be required with the `-g` option. If you do not use `-g`, then you need to add the apigeetool command to your PATH manually. Typically, the `-g` option places modules in: `/usr/local/lib/node_modules/apigee-127` on *nix-based machines.
34+
*NOTE*: The `-g` option places the apigeetool command in your PATH. On "\*nix"-based machines, `sudo` may be required with the `-g` option. If you do not use `-g`, then you need to add the apigeetool command to your PATH manually. Typically, the `-g` option places modules in: `/usr/local/lib/node_modules/apigeetool-node` on *nix-based machines.
3535

3636
# <a name="whatyouneed"></a>What you need to know about apigeetool
3737

3838
You must have an account on Apigee Edge to perform any `apigeetool` functions. These functions include:
3939

4040
* deploying an API proxy or shared flow to Edge,
4141
* undeploying an API proxy or shared flow from Edge,
42-
* deploying Node.js apps to Edge,
4342
* listing deployed API proxies or shared flows on Edge,
4443
* retrieving deployed proxies or shared flows from Edge,
4544
* deleting proxy or shared flow definitions from Edge, and
46-
* retreiving log messages from Node.js apps deployed to Edge.
4745
* create or delete an API product in Edge
4846
* create or delete a Developer in Edge
4947
* create or delete a Developer Application in Edge
@@ -57,7 +55,7 @@ You must have an account on Apigee Edge to perform any `apigeetool` functions. T
5755
* assign, remove, verify Users for a Role
5856
* list all Users in a Role
5957

60-
You need to be familiar with basic concepts and features of Apigee Edge such as API proxies, organizations, and environments.
58+
Obviously, this tool is only useful if you are familiar with basic concepts and features of Apigee Edge such as API proxies, organizations, environments, products, and so on.
6159

6260
For more information, refer to the [Apigee Edge docs](http://apigee.com/docs/).
6361

0 commit comments

Comments
 (0)