make it clear project tokens can't be used to trigger a pipeline

Author: rosieyohannan

src-api/source/includes/_builds_and_jobs.md

@@ -404,12 +404,12 @@ curl -X POST https://circleci.com/api/v1.1/project/:vcs-type/:username/:project/
   }
 ```
 
-**`POST` Request:** Triggers a pipeline of the specified project, by branch, revision, or tag. Workflows will be run or scheduled in the same way as when a webhook from source control is received.
+**`POST` Request:** Triggers a pipeline of the specified project, by branch, revision, or tag. Workflows will be run or scheduled in the same way as when a webhook from source control is received. The use of this endpoint requires a personal API token.
 
 
 <aside class="notice">
 <strong>Note:</strong> This endpoint does not yet support the <code>build_parameters</code> options that the job-triggering endpoint supports.
-This also means that this endpoint is not available for CircleCI Server.
+This also means that this endpoint is not available for CircleCI server.
 </aside>
 
 **Parameter** | **Description**

src-api/source/includes/_overview.md

@@ -64,7 +64,7 @@ curl -u <circle-token>: "https://circleci.com/api/..."
 curl "https://circleci.com/api/v1.1/me?circle-token=<circle-token>"
 ```
 
-You can add the API token using your [account dashboard](https://circleci.com/account/api). Both personal and project API tokens are supported for API v1, however, we recommend using personal API tokens at this time as project API tokens are **not** supported for API v2.
+You can add the API token using your [account dashboard](https://circleci.com/account/api). We recommend using **personal API tokens** at this time as project API tokens are **not** supported for API v2. Project API tokens are supported for a subset of API v1 endpoints.
 
 To be authenticated by the API server, use this as the value of the Circle-Token header: