Skip to content

Commit

Permalink
Fix several typos
Browse files Browse the repository at this point in the history
Signed-off-by: Sukey <[email protected]>
  • Loading branch information
sukey2008 authored Oct 28, 2023
1 parent 63b75db commit 35f3167
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/rfc/000-rfc-format.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Summary

This is an RFC to propose RFC format for Leo language.
This is a RFC to propose RFC format for Leo language.

# Motivation

Expand All @@ -12,19 +12,19 @@ This section describes proposed solution.

## Store RFCs inside Leo repository.

At early stages it is for better to see changes with the code eliminating the need to keep track of a different repository.
At early stages it is better to see changes with the code eliminating the need to keep track of a different repository.

## Use standard PR mechanics for submitting new RFCs

New RFCs should be submitted as a PRs into Leo repository. PRs should be correctly labeled for easier search. Yet they should not have number unless PR is accepted by leo maintainers.
New RFCs should be submitted as PRs into the Leo repository. PRs should be correctly labeled for easier search. Yet they should not have a number unless the PR is accepted by leo maintainers.

## Increase approvals count for RFCs

RFCs may propose changes affecting multiple systems or projects. They also introduce new changes to the language design or structure. Because of that they should be watched more carefully by as many involved team members as possible. Increasing number of required approvals should help achieve this goal.

## Format

For bootstrapping new requests template is made and placed into RFC folder.
For bootstrapping new requests, a template is made and placed into the RFC folder.

## Number

Expand Down

0 comments on commit 35f3167

Please sign in to comment.