gbdev/rgbds
1
0
Fork 0
mirror of https://github.com/gbdev/rgbds.git synced 2025-11-20 18:22:07 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix some reStructuredText

Browse Source
This commit is contained in:
Rangi42
2024-02-18 14:09:37 -05:00
parent 8a49a0b714
commit f1b6ef204d
3 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
CONTRIBUTING.rst
View File

@@ -59,8 +59,8 @@ but doesn't know that there's someone working on it.
Note that you must contribute all your changes under the MIT License. If you are Note that you must contribute all your changes under the MIT License. If you are
just modifying a file, you don't need to do anything (maybe update the copyright just modifying a file, you don't need to do anything (maybe update the copyright
years). If you are adding new files, you need to use the correct header with the years). If you are adding new files, you need to use the ``SPDX-License-Identifier: MIT``
copyright and the reference to the MIT License. header.
1. Fork this repository. 1. Fork this repository.
@@ -80,4 +80,4 @@ copyright and the reference to the MIT License.
6. Create a pull request against the branch ``master``. 6. Create a pull request against the branch ``master``.
7. Be prepared to get some comments about your code and to modify it. Tip: Use 7. Be prepared to get some comments about your code and to modify it. Tip: Use
``git rebase -i origin/master`` to modify chains of commits. ``git rebase -i origin/master`` to modify chains of commits.

2
README.rst
View File

@@ -102,7 +102,7 @@ The RGBDS source code file structure is as follows:
* ``bash_compl`` contains tab completion scripts for use with bash. Run them with ``source`` * ``bash_compl`` contains tab completion scripts for use with bash. Run them with ``source``
somewhere in your ``.bashrc``, and they should load every time you open a shell. somewhere in your ``.bashrc``, and they should load every time you open a shell.
- ``include/`` - header files for the respective source files in `src`. - ``include/`` - header files for the respective source files in ``src``.
- ``man/`` - manual pages. - ``man/`` - manual pages.

2
RELEASE.rst
View File

@@ -65,4 +65,4 @@ GitHub.
6. Click the "Publish release" button to publish it! 6. Click the "Publish release" button to publish it!
7. Update the `release` branch. You can use ``git push origin release``. 7. Update the ``release`` branch. You can use ``git push origin release``.