Merge branch 'main' into fix/2259

Manny27nyc · Dec 22, 2020 · 89bc816 · 89bc816
2 parents ddd6da2 + fb30f5b
commit 89bc816
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/...enticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md b/...enticating-to-github/generating-a-new-ssh-key-and-adding-it-to-the-ssh-agent.md
@@ -127,7 +127,7 @@ Before adding a new SSH key to the ssh-agent to manage your keys, you should hav
 1. Ensure the ssh-agent is running. You can use the "Auto-launching the ssh-agent" instructions in "[Working with SSH key passphrases](/articles/working-with-ssh-key-passphrases)", or start it manually:
   ```shell
   # start the ssh-agent in the background
-  $ eval $(ssh-agent -s)
+  $ eval `ssh-agent -s`
   > Agent pid 59566
   ```
 

diff --git a/...laborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md b/...laborating-with-issues-and-pull-requests/creating-a-pull-request-from-a-fork.md
@@ -3,7 +3,7 @@ title: Creating a pull request from a fork
 intro: You can create a pull request to propose changes you've made to a fork of an upstream repository.
 redirect_from:
   - /articles/creating-a-pull-request-from-a-fork
-permissions: Anyone with write access to a repository can create a pull request from user-owned fork.
+permissions: Anyone with write access to a repository can create a pull request from a user-owned fork.
 versions:
   free-pro-team: '*'
   enterprise-server: '*'

diff --git a/content/rest/overview/resources-in-the-rest-api.md b/content/rest/overview/resources-in-the-rest-api.md
@@ -271,7 +271,7 @@ Verb | Description
 `HEAD` | Can be issued against any resource to get just the HTTP header info.
 `GET` | Used for retrieving resources.
 `POST` | Used for creating resources.
-`PATCH` | Used for updating resources with partial JSON data.  For instance, an Issue resource has `title` and `body` attributes.  A PATCH request may accept one or more of the attributes to update the resource.  PATCH is a relatively new and uncommon HTTP verb, so resource endpoints also accept `POST` requests.
+`PATCH` | Used for updating resources with partial JSON data. For instance, an Issue resource has `title` and `body` attributes. A `PATCH` request may accept one or more of the attributes to update the resource.
 `PUT` | Used for replacing resources or collections. For `PUT` requests with no `body` attribute, be sure to set the `Content-Length` header to zero.
 `DELETE` |Used for deleting resources.