[nongnu] elpa/sesman ec275e2e10 009/100: Readme

[ELPA Syncer]

branch: elpa/sesman
commit ec275e2e10402891bede27be6764f9310c5e108b
Author: Vitalie Spinu <spinuvit@gmail.com>
Commit: Vitalie Spinu <spinuvit@gmail.com>

    Readme
---
 README.md | 10 +++++-----
 sesman.el |  2 +-
 2 files changed, 6 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index 7a37e51c71..28c367eff6 100644
--- a/README.md
+++ b/README.md
@@ -11,9 +11,9 @@ For Emacs based IDEs, session is commonly composed of one or 
more physical proce
 
   - "session" is a list of the form `(session-name ..other-stuff..)` where 
`..other-stuff..` is system dependent.
   - "system" is generic name used for a tool which uses sesman (e.g. `CIDER`, 
`ESS` etc)
-  - "contexts" are Emacs objects which describe current context. For example 
`current-buffer`, `default-directory` and `project-current` are such contexts. 
Context objects are used to create associations (links) between the current 
context and sessions. At any given time the user can link (unlink) sessions to 
(from) contexts. By default there are three types of contexts - buffer, 
directory and project, but systems can define their own contexts.
+  - "contexts" are Emacs objects which describe current context. For example 
`current-buffer`, `default-directory` and `project-current` are such contexts. 
Context objects are used to create associations (links) between the current 
context and sessions. At any given time the user can link (unlink) sessions to 
(from) contexts. By default there are three types of contexts - buffer, 
directory and project, but systems can define their own specialized context 
types..
   
-Sesman is composed of two parts, [user interface][], available as [sesman 
map][], and [system interface][] consisting of a few generic functions for 
which each systems should define its own methods. 
+Sesman is composed of two parts, [user interface][], available as a [sesman 
map][] and menu, and [system interface][] consisting of a few generics and API 
functions.
 
 ### [User Interface][]
 
@@ -43,9 +43,9 @@ Systems could directly use user level commands to manage 
sessions (`sesman-start
 Systems should link [semsna map][] into their modes' key-maps (ideally on `C-c 
C-s`, which is a good mnemonic, is free in CIDER and already does similar 
things in ESS).
 
 
-[user interface]: https://github.com/vspinu/sesman/blob/master/sesman.el#L53
-[system interface]: https://github.com/vspinu/sesman/blob/master/sesman.el#L133
-[sesman map]: https://github.com/vspinu/sesman/blob/master/sesman.el#L112-L130
+[user interface]: https://github.com/vspinu/sesman/blob/master/sesman.el#L55
+[system interface]: https://github.com/vspinu/sesman/blob/master/sesman.el#L216
+[sesman map]: https://github.com/vspinu/sesman/blob/master/sesman.el#L168
 
 [cider]: https://github.com/clojure-emacs/cider
 [ess]: https://ess.r-project.org/
diff --git a/sesman.el b/sesman.el
index 2153f06a20..9d432de060 100644
--- a/sesman.el
+++ b/sesman.el
@@ -213,7 +213,7 @@ sessions."
                        sesman-menu))
 
 
-;;; System Generic
+;;; System Generics
 
 (defvar-local sesman-system nil
   "Name of the system managed by `sesman'.