diff --git a/content/actions/creating-actions/releasing-and-maintaining-actions.md b/content/actions/creating-actions/releasing-and-maintaining-actions.md
index b189fad69d..d3e1841799 100644
--- a/content/actions/creating-actions/releasing-and-maintaining-actions.md
+++ b/content/actions/creating-actions/releasing-and-maintaining-actions.md
@@ -74,7 +74,7 @@ Here is an example process that you can follow to automatically run tests, creat
 
 Unlike some other automated release management strategies, this process intentionally does not commit dependencies to the `main` branch, only to the tagged release commits. By doing so, you encourage users of your action to reference named tags or `sha`s, and you help ensure the security of third party pull requests by doing the build yourself during a release.
 
-Using semantic releases means that the users of your actions can pin their workflows to a version and know that they might continue to receive the latest stable, non-breaking features, depending on their comfort level:
+Using semantic releases means that the users of your actions can pin their workflows to a version and know that they might continue to receive the latest stable, non-breaking features, depending on their comfort level.
 
 ## Working with the community