Skip to content

Fix more typos - #454

Open
mgabka wants to merge 1 commit into
ARM-software:mainfrom
mgabka:more_typos_fixes
Open

Fix more typos#454
mgabka wants to merge 1 commit into
ARM-software:mainfrom
mgabka:more_typos_fixes

Conversation

@mgabka

@mgabka mgabka commented Aug 19, 2026

Copy link
Copy Markdown
Contributor

It fixes more grammar issues in README.md. and acle.md


name: Pull request
about: Technical issues, document format problems, bugs in scripts or feature proposal.


Thank you for submitting a pull request!

If this PR is about a bugfix:

Please use the bugfix label and make sure to go through the checklist below.

If this PR is about a proposal:

We are looking forward to evaluate your proposal, and if possible to
make it part of the Arm C Language Extension (ACLE) specifications.

We would like to encourage you reading through the contribution
guidelines
, in particular the section on submitting
a proposal
.

Please use the proposal label.

As for any pull request, please make sure to go through the below
checklist.

Checklist: (mark with X those which apply)

  • If an issue reporting the bug exists, I have mentioned it in the
    PR (do not bother creating the issue if all you want to do is
    fixing the bug yourself).
  • I have added/updated the SPDX-FileCopyrightText lines on top
    of any file I have edited. Format is SPDX-FileCopyrightText: Copyright {year} {entity or name} <{contact informations}>
    (Please update existing copyright lines if applicable. You can
    specify year ranges with hyphen , as in 2017-2019, and use
    commas to separate gaps, as in 2018-2020, 2022).
  • I have updated the Copyright section of the sources of the
    specification I have edited (this will show up in the text
    rendered in the PDF and other output format supported). The
    format is the same described in the previous item.
  • I have run the CI scripts (if applicable, as they might be
    tricky to set up on non-*nix machines). The sequence can be
    found in the contribution
    guidelines
    . Don't
    worry if you cannot run these scripts on your machine, your
    patch will be automatically checked in the Actions of the pull
    request.
  • I have added an item that describes the changes I have
    introduced in this PR in section Changelog for year 20xx (this year)
    of section Preface/About this document.
    Create Changelog for year 20xx if it does not exist. Notice that
    changes that are not modifying the content and rendering of the
    specifications (both HTML and PDF) do not need to be listed.
  • When modifying content and/or its rendering, I have checked the
    correctness of the result in the PDF output (please refer to the
    instructions on how to build the PDFs
    locally
    ).
  • Please DO NOT add my GitHub profile to the list of contributors
    in the README page of the project.

@mgabka
mgabka requested review from Lukacma and rgwott August 19, 2026 11:26
Comment thread README.md
corrections.

The PDF version of the documents can be retrieved from the
The PDF versions of the documents can be retrieved from the

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not strictly agree with this, but it also works.

Comment thread README.md
## Contributors ✨

Thanks goes to these wonderful people ([emoji key](https://allcontributors.org/en/reference/emoji-key/)):
Thanks go to these wonderful people ([emoji key](https://allcontributors.org/en/reference/emoji-key/)):

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

While we are at it, I would suggest:
We thank the following wonderful contributors (emoji key):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants