Addressed reviewers + nit

nit: Removed a space before a dot at the 'Commit Access' link.

Author: paschalis-mpeis

llvm/docs/GitHub.rst

@@ -264,13 +264,13 @@ Your options are as follows:
 
    This approach allows GitHub to display clean, incremental diffs for each PR
    in the stack, making it much easier for reviewers to see what has changed at
-   each step. Once `feature_1` is merged, GitHub would automatically rebase and
+   each step. Once `feature_1` is merged, GitHub will automatically rebase and
    re-target your branch `feature_2` to `main`. For more complex stacks, you can
    perform this step using the web interface.
 
    This approach requires
-   `Commit Access <https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access>`_
-   . However, if you are involved with a Stacked PR, there's a good chance you'll
+   `Commit Access <https://llvm.org/docs/DeveloperPolicy.html#obtaining-commit-access>`_.
+   However, if you are involved with a Stacked PR, there's a good chance you'll
    be granted access.
 
 #. Two PRs with a dependency note
@@ -279,7 +279,6 @@ Your options are as follows:
    note in the PR summary indicating that it depends on PR_1 (e.g.,
    “Depends on #PR_1”).
 
-   The disadvantage of this approach is that GitHub will not show a clean diff.
    To make review easier, make it clear which commits are part of the base PR
    and which are new, e.g. "The first N commits are from the base PR". This
    helps reviewers focus only on the incremental changes.