Skip to content

Commit cf49ca4

Browse files
committed
Fix grammars
1 parent 89a687f commit cf49ca4

File tree

2 files changed

+3
-4
lines changed

2 files changed

+3
-4
lines changed

Development Process.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
## Roadmap
22

3-
The team has a 6-12 months high level [[Roadmap]] which defines high level themes and features to be addressed in this timeframe.
3+
The team has a 6-12 months high-level [[Roadmap]], which defines high-level themes and features to be addressed in this timeframe.
44

55
## Iterations
66

@@ -13,7 +13,7 @@ The six-week-cycle is commonly adopted in the web development ecosystem. E.g., t
1313
We work in weekly segments:
1414
- **Week 1-2**:
1515
- Address critical issues uncovered in the previous iteration
16-
- Reduce debt introduced in the previous iteration
16+
- Reduce debt introduced during the last iteration
1717
- Plan the next iteration
1818
- **Week 3-5**: Work according to the plan
1919
- **Final Week**: Endgame
@@ -22,4 +22,3 @@ We work in weekly segments:
2222
- **Week 1 (next iteration)**:
2323
- monitoring the pre-release and fixing critical issues.
2424
- publish the release to the ‘latest’ channel, sometime midweek, after 24 hours with no changes to the pre-release.
25-

Release Process.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,4 +14,4 @@ The Git workflow used in this project is largely inspired by [Gitflow workflow](
1414
* If no urgent regressions have been reported in **3 days**:
1515
* run `npm dist-tag add {{package-name}} latest` for all the packages in this repository
1616
* Go to the Releases page and uncheck the `This is a pre-release` option for this release
17-
* Otherwise, fix the bugs, and start over to release a new version from the `next` branch. But this time the new version string should be bumped as patch.
17+
* Otherwise, fix the bugs, and start over to release a new version from the `next` branch. But this time, the new version string should be bumped as a patch.

0 commit comments

Comments
 (0)