Copilot commented on code in PR #2021:
URL: https://github.com/apache/apisix-website/pull/2021#discussion_r3061463771
##########
blog/en/blog/2021/11/30/use-apisix-ingress-in-kubesphere.md:
##########
@@ -10,7 +10,7 @@ keywords:
- Kubenetes
Review Comment:
The keywords include a misspelling ("Kubenetes"). This should be corrected
to "Kubernetes" to avoid SEO/tagging issues.
```suggestion
- Kubernetes
```
##########
blog/en/blog/2022/02/25/consul-api-gateway.md:
##########
@@ -14,7 +14,7 @@ keywords:
- Consul
- Service Discovery
- Servici Register
Review Comment:
The keyword list contains a typo: "Servici Register". Since this PR is
already editing frontmatter for SEO, it’s worth correcting this to "Service
Register" (or the intended phrasing) to avoid indexing the misspelling.
```suggestion
- Service Register
```
##########
blog/en/blog/2021/01/11/interview-Apache-APISIX-contributor-Wang-Pengcheng-Senior-Security-Advisor-of-PwC-South-China-Data-Security-and-Privacy-Protection-Team.md:
##########
@@ -1,5 +1,5 @@
---
-title: Apache APISIX Contributor Interview | Pengcheng Wang from
PricewaterhouseCoopers
+title: "APISIX CVE-2020-13945: Admin API Token Flaw"
Review Comment:
The updated title reads like a CVE advisory, but the article content is
primarily an interview (the slug also includes "interview"). Consider revising
the title to reflect the interview format while still including the CVE ID, to
avoid a mismatch between title and page content/search intent.
```suggestion
title: "Interview: Pengcheng Wang on APISIX CVE-2020-13945"
```
##########
blog/en/blog/2021/07/14/the-road-to-customization-of-Sina-Weibo-API-gateway-based-on-Apache-APISIX.md:
##########
@@ -8,7 +8,7 @@ keywords:
- Weibo
- Usser Case
Review Comment:
The keywords include a misspelling ("Usser Case"). Since the frontmatter is
being updated here, please correct it (e.g., "User Case" or "Use Case",
whichever is intended) so the tag/keyword is consistent and searchable.
```suggestion
- Use Case
```
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
