diff --git a/engine/dev.sh b/engine/dev.sh
index 909ea2e..4e9aa67 100755
--- a/engine/dev.sh
+++ b/engine/dev.sh
@@ -23,4 +23,4 @@ pipeblue() {while read line; do blue $line; done}
 tee >(lorri watch | sed 's/^/[lorri] /' | pipegreen ) \
   >(./engine/serve.sh | sed 's/^/[http] /' | pipeyellow) \
   >(./engine/auto-build.sh | sed 's/^/[make] /' | pipeblue) \
-  >(sleep 1 && open 'http://127.0.0.1:3000')
+  >(sleep 1 && open 'http://127.0.0.1:3077')
diff --git a/src/posts/0022-eternal-language/index.org b/src/posts/0022-eternal-language/index.org
index 1e28133..6d3e20d 100644
--- a/src/posts/0022-eternal-language/index.org
+++ b/src/posts/0022-eternal-language/index.org
@@ -14,10 +14,13 @@ Retro compatibility, languages, etc…
 I would like to provide a better definition for "Eternal Language".
 
 #+begin_definition
-An /eternal programming language/ is a language for which code written today will still
-compile and work any time in the future but also in the past.
+*Definition:* An /eternal programming language/ is a language for which code
+written today will still compile and work any time in the future but also
+in the past.
 #+end_definition
 
+So any new feature introduced in the language should not break anything.
+
 By this definition it provide a great deal of constraint on the language
 but provide a tremendous amount of advantages.