Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Small capitalization issue #3068

Open
dilipbheda opened this issue Jan 1, 2025 · 0 comments
Open

Small capitalization issue #3068

dilipbheda opened this issue Jan 1, 2025 · 0 comments
Labels
Awaiting Triage Issues awaiting triage. See Training Team handbook for how to triage issues. [Content] Experienced Author Content development issue where the content creator is an experienced author. [Content] Feedback Feedback provided about content on Learn.

Comments

@dilipbheda
Copy link

dilipbheda commented Jan 1, 2025

Type of feedback

//content

Description

When I started reviewing the tutorial Using the WordPress REST API [https://learn.wordpress.org/tutorial/using-the-wordpress-rest-api/], I noticed a small capitalization issue in the content below.

REST stands for REpresentational State Transfer, which is a software architectural style that describes a uniform interface between physically separate components.

It should look like this:

REST stands for Representational State Transfer, which is a software architectural style that describes a uniform interface between physically separate components.

Step-by-step reproduction instructions (optional)

Please list the steps needed to reproduce or verify the feedback. For example:

  1. Go to https://learn.wordpress.org/tutorial/using-the-wordpress-rest-api/
  2. Search for REST stands for [REpresentational State Transfer](https://en.wikipedia.org/wiki/Representational_state_transfer)

Ref: https://learn.wordpress.org/tutorial/using-the-wordpress-rest-api/#:~:text=one%20of%20them.-,REST%20stands%20for%20REpresentational%20State%20Transfer%2C%20which%20is%20a%20software%20architectural%20style%20that%20describes%20a%20uniform%20interface%20between%20physically%20separate%20components.,-At%20it%E2%80%99s%20core

@dilipbheda dilipbheda added [Content] Experienced Author Content development issue where the content creator is an experienced author. Awaiting Triage Issues awaiting triage. See Training Team handbook for how to triage issues. labels Jan 1, 2025
@github-actions github-actions bot added the [Content] Feedback Feedback provided about content on Learn. label Jan 2, 2025
@github-project-automation github-project-automation bot moved this to Awaiting Validation in LearnWP Content - Feedback Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Awaiting Triage Issues awaiting triage. See Training Team handbook for how to triage issues. [Content] Experienced Author Content development issue where the content creator is an experienced author. [Content] Feedback Feedback provided about content on Learn.
Projects
Status: Awaiting Validation
Development

No branches or pull requests

1 participant