27 Matching Annotations
  1. May 2017
    1. the previous section

      instead of next/previous, above/below we should use specific titles.

    1. Webhooks are basically a URL where you need to POST data to

      Something wrong with the grammar here.

    1. Team admins can use the “Track Usage” link on the monitor dashboard to check how many requests the team has made that month

      Show sample screenshot.

    1. mock service

      "mock servers". Define in the line below that Postman provides this as a service of Postman Pro.

    1. on the  icon in header bar

      Need smaller icon and smaller screenshot.

    1. The easiest way to get started with the API is to click the Run in Postman button

      Embed the run in postman button below

    1. Head to the billing page, and click ‘Change Plan’ in the settings dropdown.

      Add a screenshot of the billing page for this state.

    2. Click the “Configure next cycle” link on the billing page to switch to the monthly plan / change team size for the next cycle. If you switch to the monthly plan, you’ll be charged at $8/user/month after your billing cycle ends

      Add a screenshot of the billing page.

    1. Postman’s vision is to help you build a super fast and smooth workflow for API development keeping some key questions in mind:

      Kasy can edit/re-write with respect to the new messaging.

    1. enter Team Domain

      whose Team Domain?

    2. There are two ways of doing this.

      This tutorial is not very clear. Needs to be rephrased in multiple places.

    3. user will log into Postman using configured Identity provider

      which user?

    4. Single Sign-On for Users

      Needs some copy editing.

    1. Most SAML 2.0 compliant identity providers require the same information about the service provider for setup (Postman is the service provider). These values are specific to a Postman Team and are available after configuring SSO in the Edit Team Page.

      Too much spacing between lines.

    2. are automatically logged

      "is automatically logged"

    3. SSO is a user authentication service that permits

      "SSO services permit a user..."

    1. Your credentials (e.g. email, username) will not be shared.

      Remove this line.

    2. who generates the collection

      "generates the Run in Postman embed code from their collection"

    1. // Existing environment named 'user_data' // { // auth_token: 'q4yugoiwqu4hlrjksfdm3897ryq3891s', // user_id: '823', // session_data: {} // }

      Remove this snippet. Not clear why this is here. Explain separately from the snippet. "Let's say there is an existing environment "user_data" with the following values"

    2. create a new environment using API keys entered by your user

      The example is not clear. "entered" where?

    1. To update the collection that users see when they use the Run in Postman button, you’ll need to update the collection link. 

      Add another line before this: If you have made updates to the collection, these changes will not be automatically pushed to the Run in Postman button and you will have to update your collection manually.

    1. Continuous Integration

      Define what is Continuous Integration with a paragraph.