Skip to content
This repository was archived by the owner on Feb 12, 2024. It is now read-only.

Made Standard Readme Compliant #324

Merged
merged 1 commit into from
Jun 23, 2016
Merged

Conversation

RichardLitt
Copy link
Member

Let me know what you think!

# Installation

## npm
## Table of Contents
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't it be "Table of contents", to follow the same as "Project status"

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, I think it is OK like this. Table of Contents is normally capped, AFAIK.

@RichardLitt RichardLitt force-pushed the feature/standard-readme-compliancy branch 2 times, most recently from 4444ffb to 1edc4ac Compare June 23, 2016 08:57
Let me know what you think!
@RichardLitt RichardLitt force-pushed the feature/standard-readme-compliancy branch from 1edc4ac to 5705957 Compare June 23, 2016 08:57
@daviddias
Copy link
Member

Thank you :)

@daviddias daviddias merged commit 62cc2a5 into master Jun 23, 2016
@daviddias daviddias deleted the feature/standard-readme-compliancy branch June 23, 2016 14:06
@jbenet jbenet removed the status/in-progress In progress label Jun 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants