Making WordPress.org

#6542 closed defect (bug) (fixed)

Some typos in 'Plugin Handbook -> HTTP API' page

Reported by: hztyfoon's profile hztyfoon Owned by:
Milestone: Priority: normal
Component: Handbooks Keywords:
Cc:

Description

in this page: https://developer.wordpress.org/plugins/http-api/

there are some typos:

  • in the Introduction section, the word 'with' used twice in "The WordPress HTTP API can also be used to communicate and interact with with other APIs like..."
  • in the Response codes section, the word 'the' used twice in "Rather than go into a lengthy explanation of each, here are the the standard."
  • in the Code Classes -> Common Codes section, there should be 'common'(not plural 'commons') in "These are the most commons codes you will encounter."
  • in the GETting data from an API section, there should be 'follow redirects' instead of 'follow redirections' in "redirection – 5 – How many times to follow redirections."
  • in the HEADing off bandwidth usage section, 'the' should be used before 'number of requests' in "On high traffic APIs, GET is often limited to ('the' added after the word 'to') the number of requests per minute or hour.". also, in the same section, the word 'are' used twice in "Going back to the GitHub example, here are are few headers to watch out for."
  • in the WordPress Transients section, the word 'function' should be plural 'functions' in "There are only three function to do all the heavy lifting for you."
  • in the Introduction to caching section, the 'set up' should be used instead setup in "What follows is just an introduction to caching and a simple yet effective way to quickly setup a cache for API responses."

Change History (1)

#1 in reply to: ↑ description @dd32
20 months ago

  • Resolution set to fixed
  • Status changed from new to closed

Thanks! For brevity, assume I've done the above changes unless noted here:

Replying to hztyfoon:

  • in the HEADing off bandwidth usage section, 'the' should be used before 'number of requests' in "On high traffic APIs, GET is often limited to ('the' added after the word 'to') the number of requests per minute or hour.".

I've gone with a, as in GET is often limited to a number of requests per minute or hour.

  • in the Introduction to caching section, the 'set up' should be used instead setup in "What follows is just an introduction to caching and a simple yet effective way to quickly setup a cache for API responses."

As it's a verb in this context I think, so set up is correct: https://grammarist.com/spelling/set-up-vs-setup/

Note: See TracTickets for help on using tickets.