Changed spelling and corrected grammar.

Changed spelling and corrected grammar. Also fixed a part of the HTML code.

README.md

@@ -90,10 +90,10 @@ The core team, maintainers and outside contributors are encouraged to follow the
 * Do not create arbitrary branches or push directly to the central repo `master` or `development` branches.
 * Do not force push branches.
 * Avoid rebasing branches of open PRs to help preserve conversation history.
-* Authors must always request a review for their PRs, Exception: It does not alter any logic (e.g. comments, dependencies, docs, file organisation), then it may merged once CI checks are complete.
+* Authors must always request a review for their PRs, Exception: It does not alter any logic (e.g. comments, dependencies, docs, file organisation), then it may be merged once CI checks are complete.
 * Author should avoid merging their own PR, if it hasn't been reviewed and approved.
 * If travis or other CI integrations are configured for the repo, avoid merging PRs that fail checks.
-* When the maintainer is opening a PRs they must still request review from a core team member.
+* When the maintainer is opening a PRs they must still request a review from a core team member.
 
 Each repository may have contributing guidelines detailed in their README files.
 The maintainer must ensure this contribution section is linked to as the base guideline.
@@ -173,8 +173,7 @@ Until the Joystream mainnet goes live, a sequence of test networks will be rolle
 | Mesopotamia     | 21.12.18          |   28.02.19    |       N/A        |
 
 <br />
-<
-src="img/pm-section_new.svg" id="project-management"/>
+<img src="img/pm-section_new.svg" id="project-management"/>
 
 ## Why is this on GitHub?
 
@@ -362,7 +361,7 @@ In addition to the weekly follow-up meetings addressed above, each release cycle
 
 - `Launch Meeting`
 - `User Stories Meeting`
-- `Release Plan Finalization Meeting]`
+- `Release Plan Finalization Meeting`
 - `Release Checklist Meeting`
 - `Lessons Learned`
 

meetings/rome/README.md

@@ -150,7 +150,7 @@ Schedule [user stories meeting](#user-stories-meeting)
 
 #### Item 3
 
-This was not addresssed.
+This was not addressed.
 
 **Other topics raised:**
 NA
@@ -329,7 +329,7 @@ PodcastGuestAppearance {
 - to be able to participate in competitions and win real money.
 - to be able to propose increasing participation payouts.
 - a forum category to discuss and evaluate proposals.
-- insight on what Council Members thinks about proposals.
+- insight on what Council Members think about proposals.
 
 ##### As a Council Member candidate, I want
 - to communicate to stakeholders how I would allocate the resources as part of my campaign.
@@ -649,7 +649,7 @@ We kept quite strictly to the schedule laid out [here](sprint-in-london.md) for
 - It would have been nicer to have a more comprehensive plan for the sprint. This would have allowed for preparing in advance the things which could be shared with others (e.g. mockups).
 - We (eventually) got to spend valuable time on problems that are easier solved together: standing in front of a shared screen/whiteboard discussing design and data models.
 - We should have avoided excessive focus on tracking progress, no fun, adds little value.
-- We should have had daily "standup" at a specific time to help efficiently starting collabration each day.
+- We should have had daily "standup" at a specific time to help efficiently starting collaboration each day.
 - Best time for a sprint is perhaps super early in a release, or with more RnD/experimental focus, rather than tied to shipping.
 - We didn't always stick to schedule.
 - It was very good for morale for everyone to meet each other.

testnets/README.md

@@ -15,7 +15,7 @@ Table of Contents
 
 # Overview
 This directory contains data on [live](#live-testnet), [next](#next-testnet) and [past](#past-testnets) testnets.
-It also contains templates for for planning releases.
+It also contains templates for planning releases.
 
 # Testnet Releases
 

testnets/rome/specification/runtime/forum-module.md

@@ -89,7 +89,7 @@ There is a maximum depth to a category tree. This is because doing any mutation
 
 - `postById`: Map `Post` identifier to corresponding instance.
 
-- `nextPostId`: Identifier value to be used for for next `Post` created.
+- `nextPostId`: Identifier value to be used for next `Post` created.
 
 - `forumSudo`: Optional `ForumSudoId` of forum sudo.