From 0c0eb1275d4dadbfa88b66f4caa2e3f24495bb63 Mon Sep 17 00:00:00 2001 From: Tenghuan He Date: Fri, 15 Apr 2022 00:15:17 +0800 Subject: [PATCH] Fix minor typos in README.md Signed-off-by: tenghuanhe --- README.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index c865cc8a..0e7298b9 100644 --- a/README.md +++ b/README.md @@ -21,14 +21,14 @@ process: 1. Start a discussion on the [slf4j-dev mailing list](http://www.slf4j.org/mailing-lists.html) about your proposed change. Alternately, file a [bug -report](http://www.slf4j.org/bug-reporting.html) to initiatite the +report](http://www.slf4j.org/bug-reporting.html) to initiate the discussion. Note that we ask pull requests to be linked to a [Jira ticket](https://jira.qos.ch/). 2. Fork qos-ch/slf4j. Ideally, create a new branch from your fork for your contribution to make it easier to merge your changes back. -3. Make your changes on the branch you hopefuly created in Step 2. Be +3. Make your changes on the branch you hopefully created in Step 2. Be sure that your code passes existing unit tests. Please add unit tests for your work if appropriate. It usually is. @@ -42,7 +42,7 @@ check](https://probot.github.io/apps/dco/) application. your master! If you do it will make it harder to submit new changes later. -6. Submit a pull request to SLF4J from from your commit page on github. +6. Submit a pull request to SLF4J from your commit page on github. 7. Did we mention that you will be asked to link your pull request -with a Jira ticket? \ No newline at end of file +with a Jira ticket?