WWW-www.enlightenment.org pushed a commit to branch master.
http://git.enlightenment.org/website/www-content.git/commit/?id=8e7f72e4dc8e1f3a32d6afb598548f1e62731957
commit 8e7f72e4dc8e1f3a32d6afb598548f1e62731957
Author: Xavi Artigas <xavierarti...@yahoo.es>
Date: Mon Sep 2 07:25:26 2019 -0700
Wiki page eo-guide.md changed with summary [changed maximum line length] by
Xavi Artigas
---
pages/contrib/docs/eo-guide.md.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/pages/contrib/docs/eo-guide.md.txt
b/pages/contrib/docs/eo-guide.md.txt
index e033e0cf3..3cfe049fc 100644
--- a/pages/contrib/docs/eo-guide.md.txt
+++ b/pages/contrib/docs/eo-guide.md.txt
@@ -64,7 +64,7 @@ Bear in mind that documentation tags placed elsewhere will be
ignored and may ev
* Start all your sentences with Upper Case.
* End all your sentences with periods.
- * Keep your lines under 80 characters.
+ * Keep your lines under 120 characters.
* Document properties at the ``@property ... {`` level. In other words, do
not document the property's ``get`` and ``set`` methods (accessors)
independently. If the methods really do something other than setting and
getting a property, then put as much common text at the ``@property`` level and
only put whatever's different in the accessors.
* Start the description of methods with a verb in singular form, that is,
``Destroys the object`` and not *Destroy the object*.
* Methods returning a Boolean (like ``is_object_a_box``) should start with
the phrase ``Returns $true if`` (or ``$false``). For example: ``Returns $true
if the $object parameter is of the box type.``.
--
