Cleanup library headers

- In the summary line, use three dashes to separate the file name
  from the summary.  That is the convention, which some tools depend
  on, and for some libraries we already did it here too.

- Capitalize the first word in the summary.  That is the convention,
  and for some libraries we already did it here too.

- For libraries that have a commentary, make sure it is placed in a
  "Commentary:" section.

- Make sure the "Code:" heading, which separates the header from the
  code part of the library, exists in all files.

1 files changed, 3 insertions, 1 deletions

diff --git a/elisp/geiser-eval.el b/elisp/geiser-eval.el
index 5e4c566..8f58c25 100644
--- a/elisp/geiser-eval.el
+++ b/elisp/geiser-eval.el
@@ -1,4 +1,4 @@
-;;; geiser-eval.el -- sending scheme code for evaluation  -*- lexical-binding: t; -*-
+;;; geiser-eval.el --- Sending scheme code for evaluation  -*- lexical-binding: t; -*-
 
 ;; Copyright (C) 2009, 2010, 2011, 2012, 2013, 2015, 2021, 2023 Jose Antonio Ortega Ruiz
 
@@ -9,6 +9,8 @@
 
 ;; Start date: Sat Feb 07, 2009 22:35
 
+;;; Commentary:
+
 ;; Functions, building on top of geiser-connection, to evaluate scheme
 ;; code.