From 72cc02c22cd2dd7f4c42243d411103f22934f9c5 Mon Sep 17 00:00:00 2001
From: Owen Zimmerman <123591347+Owen-sz@users.noreply.github.com>
Date: Thu, 22 Oct 2026 14:48:25 -0500
Subject: [PATCH] guidelines: drop Usage of Periods in Various Package Fields
 guideline

Fedora has this already
---
 src/content/docs/contributing/guidelines.mdx | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/src/content/docs/contributing/guidelines.mdx b/src/content/docs/contributing/guidelines.mdx
index 502fa49..7fddf1f 100644
--- a/src/content/docs/contributing/guidelines.mdx
+++ b/src/content/docs/contributing/guidelines.mdx
@@ -628,9 +628,6 @@ BuildRequires:  desktop-file-utils
 %{_appsdir}/NeoHtop.desktop
 ```
 
-### Usage of Periods in Various Package Fields
-You MUST NOT have a period at the end of any <Code code={`Summary:`} lang={RPMSpec} inline /> tags, and you SHOULD have a period at the end of all <Code code={`%description`} lang={RPMSpec} inline />s.
-
 ### Usage of %elifarch
 
 To make specs easier to read, you SHOULD use <Code code={`%ifarch`} lang={RPMSpec} inline /> followed by <Code code={`%elifarch`} lang={RPMSpec} inline /> before <Code code={`%endif`} lang={RPMSpec} inline /> in specs where build steps are arch dependent.