From 8311b29083ca6d321fc4a7e82f657100a6a03030 Mon Sep 17 00:00:00 2001 From: Rich Trott Date: Mon, 28 Jun 2021 06:36:17 -0700 Subject: [PATCH] doc: use "repository" in maintaining-V8 doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Use "repository" instead of "repo". This also adjusts capitalization in a header that was already being modified to use "repository" because even I couldn't bring myself to put that in a separate commit. PR-URL: https://github.com/nodejs/node/pull/39179 Reviewed-By: Michaël Zasso Reviewed-By: Harshitha K P Reviewed-By: Richard Lau Reviewed-By: Antoine du Hamel Reviewed-By: Michael Dawson Reviewed-By: Luigi Pinca --- doc/guides/maintaining-V8.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/doc/guides/maintaining-V8.md b/doc/guides/maintaining-V8.md index da940758a25d94..3238f04a2d32fc 100644 --- a/doc/guides/maintaining-V8.md +++ b/doc/guides/maintaining-V8.md @@ -274,9 +274,9 @@ Refs: https://github.com/v8/v8/commit/a51f429772d1e796744244128c9feeab4c26a854 PR-URL: https://github.com/nodejs/node/pull/7833 ``` -* Open a PR against the `v6.x-staging` branch in the Node.js repo. Launch the - normal and [V8 CI][] using the Node.js CI system. We only needed to backport - to `v6.x` as the other LTS branches weren't affected by this bug. +* Open a PR against the `v6.x-staging` branch in the Node.js repository. Launch + the normal and [V8 CI][] using the Node.js CI system. We only needed to + backport to `v6.x` as the other LTS branches weren't affected by this bug. ### Backports identified by the V8 team @@ -382,7 +382,7 @@ git node v8 major --branch=5.1-lkgr This should be followed up with manual refloating of all relevant patches. -## Proposal: using a fork repo to track upstream V8 +## Proposal: Using a fork repository to track upstream V8 The fact that Node.js keeps a vendored, potentially edited copy of V8 in deps/ makes the above processes a bit complicated. An alternative proposal would be to