From 35f31678bf6bd9e89f3ef26e864d5401707cb5a4 Mon Sep 17 00:00:00 2001
From: Sukey <35202440+sukey2008@users.noreply.github.com>
Date: Sat, 28 Oct 2023 22:19:28 +0200
Subject: [PATCH] Fix several typos

Signed-off-by: Sukey <35202440+sukey2008@users.noreply.github.com>
---
 docs/rfc/000-rfc-format.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/rfc/000-rfc-format.md b/docs/rfc/000-rfc-format.md
index 05e4649ccb..278b4f4177 100644
--- a/docs/rfc/000-rfc-format.md
+++ b/docs/rfc/000-rfc-format.md
@@ -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
 
@@ -12,11 +12,11 @@ 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
 
@@ -24,7 +24,7 @@ RFCs may propose changes affecting multiple systems or projects. They also intro
 
 ## 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