In the Stack Exchange, Inc. API Terms of Use page, the first paragraph has a word with a spelling mistake.

The word programmatically is displayed as programatically (with single m).

... a set of programming interfaces which allow you to programatically query and connect to the Stack Exchange Network. ...


1 Answer 1


This will be fixed in the next build (rev 2018.5.29.30545).

Thanks to the comments, the commit message for this fix was a no-brainer:

commit message

  • 1
    Steak! I'm hungry. May 29, 2018 at 11:37
  • Wait... what happened to revisions 30534 and 30535? It's only 30533 now... May 29, 2018 at 11:38
  • We do not talk about 20534 and 30535. (Also, my guess would be they don't deploy every build?) May 29, 2018 at 11:42
  • @Journeyman oh, bad builds. They should be indeed left alone, never to be mentioned. ;-) (that said, who says 30536 won't be a bad build too?) May 29, 2018 at 11:56
  • There are some other gramar misteak in API documentation
    – Arulkumar
    May 29, 2018 at 11:58
  • @Arulkumar yeah, I've fixed those too (in the same commit), just needs a build
    – m0sa
    May 29, 2018 at 12:07
  • @m0sa Oh, great.
    – Arulkumar
    May 29, 2018 at 12:08
  • @ShadowWizard the last number in the build revision is propagated from the first build in our build chain (our Dev environment). So we get an incremented number every time a dev build runs / triggers (by one or more commits).
    – m0sa
    May 29, 2018 at 12:12
  • @m0sa makes sense! So it means you can't really predict the final number that will actually go live... no? May 29, 2018 at 12:14
  • exactly, but I can give you a number, and if you see a it, or a greater one, it means the fix is deployed
    – m0sa
    May 29, 2018 at 12:15
  • Well, it's done. Time to status-completed the question, no? :) May 29, 2018 at 14:49
  • whilst you're there would you mind looking at these ones too? :) May 29, 2018 at 17:42

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .