Format and language

issue-ops · Nov 1, 2023 · dc83e7a · dc83e7a
1 parent 0f3ddf6
commit dc83e7a
Show file tree

Hide file tree

Showing 4 changed files with 9 additions and 9 deletions.
diff --git a/docs/content/states-and-transitions/approve.mdx b/docs/content/states-and-transitions/approve.mdx
@@ -1,6 +1,6 @@
 ---
-title: Approved
-description: An issue is approved and processing may begin
+title: Approve
+description: The request is approved and we can process it further.
 status: Alpha
 ---
 

diff --git a/docs/content/states-and-transitions/deny.mdx b/docs/content/states-and-transitions/deny.mdx
@@ -1,6 +1,6 @@
 ---
-title: Approved
-description: An issue is approved and processing may begin
+title: Deny
+description: The request is denied and the issue can be closed.
 status: Alpha
 ---
 

diff --git a/docs/content/states-and-transitions/index.mdx b/docs/content/states-and-transitions/index.mdx
@@ -92,9 +92,9 @@ Your workflows must track the following to determine what jobs to run:
 Each of the following sections describes how to implement the core transitions
 in an IssueOps workflow. Throughout each page, you will see an example
 implementation of a new repository request workflow. This workflow is designed
-to demonstrate how to apply each concept. The full example can be found in the
-[`issue-ops/new-repository-example`](https://github.com/issue-ops/new-repository-example)
-repository.
+to demonstrate how to apply each concept.
+
+{/* TODO: The full example can be found in the [`issue-ops/new-repository-example`](https://github.com/issue-ops/new-repository-example) repository. */}
 
 - [Parse](/states-and-transitions/parse)
 - [Validate](/states-and-transitions/validate)

diff --git a/docs/content/states-and-transitions/submit.mdx b/docs/content/states-and-transitions/submit.mdx
@@ -1,6 +1,6 @@
 ---
-title: Submitted
-description: An issue is ready to be reviewed or processed.
+title: Submit
+description: Tell GitHub Actions the issue is ready for processing.
 status: Alpha
 ---