You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
File:packages/forgerock/data_stream/am_access/fields/forgerock-fields.yml (line 110) Current text:The x-forwaded-proto header of the HTTP request. Suggested fix:The x-forwarded-proto header of the HTTP request. Why: Clear typo in user-facing field description.
Also occurs in:
packages/forgerock/docs/README.md (line 136)
2. Typo: paramater → parameter
File:packages/o365_metrics/docs/README.md (line 83) Current text:By default, this paramater is \3`. **Suggested fix:**By default, this parameter is `3`.` Why: Clear spelling error in user-facing documentation.
3. Grammar: a Elastic → an Elastic
File:docs/ci_pipelines.md (line 7) Current text:...using a Elastic Serverless project. Suggested fix:...using an Elastic Serverless project. Why: Clear article-agreement grammar error.
4. Misleading text: pipeline count does not match list
File:docs/ci_pipelines.md (line 5) Current text:Currently, there are five different pipelines: Suggested fix:Currently, there are six different pipelines: Why: The list immediately below contains six pipelines, so current wording is directly contradictory.
5. Grammar: subject-verb agreement
File:docs/extend/tips-for-building.md (line 229) Current text:...a service which write the sample logs... Suggested fix:...a service which writes the sample logs... Why: Clear subject-verb agreement error.
Suggested Actions
Replace x-forwaded-proto with x-forwarded-proto in both listed ForgeRock files.
Fix paramater to parameter in packages/o365_metrics/docs/README.md.
Update a Elastic to an Elastic in docs/ci_pipelines.md.
Correct the pipeline count in docs/ci_pipelines.md from five to six.
Change which write to which writes in docs/extend/tips-for-building.md.
Note
🔒 Integrity filter blocked 1 item
The following item were blocked because they don't meet the GitHub integrity level.
#16136search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
To allow these resources, lower min-integrity in your GitHub frontmatter:
Text Improvements
The following user-facing text issues were found in the repository. Each is a low-effort fix.
1. Typo family:
x-forwaded-proto→x-forwarded-protoFile:
packages/forgerock/data_stream/am_access/fields/forgerock-fields.yml(line 110)Current text:
The x-forwaded-proto header of the HTTP request.Suggested fix:
The x-forwarded-proto header of the HTTP request.Why: Clear typo in user-facing field description.
Also occurs in:
packages/forgerock/docs/README.md(line 136)2. Typo:
paramater→parameterFile:
packages/o365_metrics/docs/README.md(line 83)Current text:
By default, this paramater is \3`.**Suggested fix:**By default, this parameter is `3`.`Why: Clear spelling error in user-facing documentation.
3. Grammar:
a Elastic→an ElasticFile:
docs/ci_pipelines.md(line 7)Current text:
...using a Elastic Serverless project.Suggested fix:
...using an Elastic Serverless project.Why: Clear article-agreement grammar error.
4. Misleading text: pipeline count does not match list
File:
docs/ci_pipelines.md(line 5)Current text:
Currently, there are five different pipelines:Suggested fix:
Currently, there are six different pipelines:Why: The list immediately below contains six pipelines, so current wording is directly contradictory.
5. Grammar: subject-verb agreement
File:
docs/extend/tips-for-building.md(line 229)Current text:
...a service which write the sample logs...Suggested fix:
...a service which writes the sample logs...Why: Clear subject-verb agreement error.
Suggested Actions
x-forwaded-protowithx-forwarded-protoin both listed ForgeRock files.paramatertoparameterinpackages/o365_metrics/docs/README.md.a Elastictoan Elasticindocs/ci_pipelines.md.docs/ci_pipelines.mdfrom five to six.which writetowhich writesindocs/extend/tips-for-building.md.Note
🔒 Integrity filter blocked 1 item
The following item were blocked because they don't meet the GitHub integrity level.
search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".To allow these resources, lower
min-integrityin your GitHub frontmatter:What is this? | From workflow: Text Auditor
Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.