Updating README

Author: datapythonista

README.md

@@ -33,7 +33,6 @@ Send a pull request adding a new file `_chapters/<your-chapter-name>.md`, where
 separating words with underscore (e.g. `london_pyton_sprints`).
 
 The content of the file should list:
-- layout: default
 - object_id: same as the name of the file, as described before (without the extension)
 - title: name of your chapter (using normal text)
 - website_link: link to your website
@@ -45,15 +44,10 @@ The content of the file should list:
 How does Jekyll work?
 ---------------------
 
-#### Create layouts (templates for django people) to generate your views
-#### Create content files with yml variables(date) and html / plain text to feed into the layouts
-#### Use scss (sass) or less to style (automatically preprocessed into css during build) - see _sass (partials)
-#### Main content goes into _pages
-#### Use Liquid templating language (similar to jinja2 / django templating languages) to create logic
-#### includes are your friends - use them as modules, functions , snippets of html or whatever
-#### time related files - _posts (see chapters_events), categories are automatically generated by jekyll using the parent folder name as the category name
-#### subject related files - collections, have to add them in _config.yml for jekyll to see them properly (see _sponsors, _chapters)
-#### Config in _config.yml
-#### Static content - images, javascript, css in static folder.
-
-#### When change pushed to master / origin - github pages rebuilds the site.
+- Posts (files in `_posts/*.md`) are the event pages in markdown
+- Projects (`_project/*.md`) are the open source projects we contribut to
+- Sponsors (`_sponsors/*.md) are the companies providing the venue and pizzas
+- Layouts (files in `_layouts/*.html`) are equivalent to Django templates,
+  and used to render the posts (events)
+- CSS is managed with scss/sass and built by Jekyll
+- GitHub pages automatically builds the site when the repository is updated