humble suggestions to specs documentation

[cage]

Hi!

I  find  gemini very  exciting,  bringing  back  some fun  in  network
programming!

I have some  small suggestions to spec style, i  apologize if this was
already  addressed in  a previous  message  (i am  lazy and  i did  not
searched archive, sorry).

       --------------
1.3.1

Gemini response headers look like this:

<STATUS> <META><CR><LF>

[...]

       --------------

In my opinion the space character between <STATUS> and <META> could be
a symbol not the character itself something like:

<STATUS><SPACE><META><CR><LF>

this  way it  is much  more difficult  that the  reader could  miss or
misunderstand the single space in the response line.

       --------------

1.4.2

[...]

1.4.3

       --------------

I think would be a good idea to include some code snippets (maybe in C
with libssl?) to illustrate how to do server validation or make client
certificate.

I the code was  too long could be added in an  appendix or some code
form an existing implementation can be linked, i do know.

I think there is a minor typo in the FAQ:

       --------------
### 1.3 Where can I learn more?

[...]

Official discussion regarding Gemini hapens on a mailing list.

[...]

       --------------

Bye and thank you for gemini!
C.