Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: Snooz82

website/docs/chapter-01/04_styles.md

@@ -16,7 +16,7 @@ While **Keyword-Driven Testing (KDT)** and **Behavior-Driven Development (BDD)**
 
 Both styles can be mixed, even within the same test or task, but it is strongly recommended to have separate styles for separate purposes and not mix them within the same body.
 One practical solution would be to define acceptance test cases that cover users' expectations in a declarative *Behavior-Driven Style*, while using keywords that are implemented in an imperative *Keyword-Driven style*.
-Further system level :term[test cases](Test Case), that are not covering acceptance criteria could be written in a *Keyword-Driven style*.
+Further system level :term[test cases]{term="Test Case"}, that are not covering acceptance criteria could be written in a *Keyword-Driven style*.
 
 The approach of both styles is different in that way,
 that the *Behavior-Driven Style* is a **declarative** specification,

website/src/components/Glossary/GlossaryTable.module.css

@@ -39,13 +39,6 @@
   table-layout: fixed;
 }
 
-.termCol {
-  width: 28%;
-}
-
-.definitionCol {
-  width: 72%;
-}
 
 th,
 td {
@@ -91,11 +84,7 @@ tbody tr {
   width: 100%;
 }
 
-.emptyState {
-  text-align: center;
-  padding: 1rem;
-  color: var(--ifm-color-emphasis-700);
-}
+
 
 .definitionText > :first-child {
   margin-top: 0;