diff --git a/docs/hyperexecute-how-to-manage-project-level-secrets.md b/docs/hyperexecute-how-to-manage-project-level-secrets.md
index 93ec3159b..f21a91e53 100644
--- a/docs/hyperexecute-how-to-manage-project-level-secrets.md
+++ b/docs/hyperexecute-how-to-manage-project-level-secrets.md
@@ -45,7 +45,7 @@ Secrets in <BrandName /> HyperExecute are encrypted environment variables used t
 Managing sensitive information like API tokens, credentials, and access keys is crucial when running tests in <BrandName /> HyperExecute. To address this, HyperExecute offers a Secrets Management system, and one of its powerful features is Project Level Secrets. This feature lets you define secrets scoped to a specific project, making secret handling more secure, easier, and collaborative for your teams.
 
 ## What Are Project Level Secrets?
-Project-level secrets are bound to a specific HyperExecute project instead of a user or account. When a job runs using that project ( referenced by id or both id and name in the YAML configuration, which is a sub-parameters of project parameter), the project-level secrets are automatically available to the test environment.
+Project-level secrets are bound to a specific HyperExecute project instead of a user or account. When a job runs using that project ( referenced by id or both id and name in the YAML configuration, which are sub-parameters of project parameter), the project-level secrets are automatically available to the test environment.
 
 ### Key Points
 - Define secrets once per project.