From 28b3f122d69e5d02001a8608ddf946a915413d73 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ville=20Skytt=C3=A4?= Date: Mon, 25 Nov 2024 08:03:53 -0100 Subject: [PATCH] docs: spelling fixes (#3512) --- README.md | 2 +- docs/examples.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 797af8c..154da90 100644 --- a/README.md +++ b/README.md @@ -99,7 +99,7 @@ Other token options: #### branch-token The action first creates a branch, and then creates a pull request for the branch. -For some rare use cases it can be useful, or even neccessary, to use different tokens for these operations. +For some rare use cases it can be useful, or even necessary, to use different tokens for these operations. It is not advisable to use this input unless you know you need to. #### commit-message diff --git a/docs/examples.md b/docs/examples.md index d2b1316..4def247 100644 --- a/docs/examples.md +++ b/docs/examples.md @@ -324,7 +324,7 @@ jobs: ### Keep a fork up-to-date with its upstream -This example is designed to be run in a seperate repository from the fork repository itself. +This example is designed to be run in a separate repository from the fork repository itself. The aim of this is to prevent committing anything to the fork's default branch would cause it to differ from the upstream. In the following example workflow, `owner/repo` is the upstream repository and `fork-owner/repo` is the fork. It assumes the default branch of the upstream repository is called `main`.