Internal Project Contribution
Tags: opensource, c, github, beginners
Published: 2021-11-19 21:12:03

In this __Release 0.3__, there are 3 different requirements. And the __second one__ is about __Internal Project Contribution__. For this internal project contribution, I selected a repository that from `IPC144`. And the issue that I selected was about Audit a `MD` file. This `MD` file is about the knowledge that we learn in __IPC144__. And the topic I selected was `Two-Dimensional-Arrays`. The __reason__ I picked this topics was I thought this is an __interesting topic__ and I wanted to __review__ the two-dimensional-arrays __content__. 

###Procedure
Here is a checklist I created to this issue:
![Checklist](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/a0gwlzpyyy83r3xhmxm7.png)
What I did was just follow the checklist. The first time that I read through the `two-dimensional-arrays.md` file, I think that it looks good! But that doesn't right! Since there is an issue, it has to have some things to improve. So, I just read the `MD` file again and I found some problems. 

__Firstly__, I found that the sentences that in each paragraph was __break by two spaces__, which is not a normal way we do in our daily life. __Secondly__, I found that the image that the `MD` file using is __missing a alt text__. __Thirdly__, I found that the code examples in the `MD` file are __indented too much__. __Last but not least__, I found that there are __a few__ `<br />` inside the `MD` file. And I can't find any of of these problems above at the first time. 

__Since__ there were many __problems__ I listed out after the second time of reading. I began to make __improvements__. 
After solved the problems that I found at the second time of reading. I told myself, "Perhaps there are more improvement you can make after your third - forth times of reading." 

__Thus__, I read the `MD` again after I fixed those problems. However, I only found two more issues after my forth times of reading. __The first one__ was the `MD` file is lack of highlighting words. This is a reading for those students in IPC144, they are new to C language. And I believe that with some highlighting words, this documentation will be easier for them to read and learn! __The second one__ was the code example in the documentation again. I found that I can make some improvement to the for loop code with `{}` so that they look better.
After these two improvements I made, I decided to make the `Pull Request`. I would like to ask help from other contributors. As long as I make the PR, they would have a chance to review my PR and they might come up with some better ideas to audit the `MD` file!

__Surprisingly__, I got 3 more [suggestions](https://github.com/Seneca-ICTOER/IPC144/pull/108) from other contributors!
__①__: A solution to make the imagine looks nicer in dark mode!
![Image_In_Dark_Mode](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/ju7053kx76zjnn9ob7qe.png)
__②__: Edit the alt text and Update the Frontmatter!
![Image_description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/2fub7daaao1k1yu7g9j9.png)
![Frontmatter](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/96sutnccjbptup3ohq6l.png)
__③__：Add admonition!
![Admonition](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/vz25jax6okwiiqksmyl6.png)

The suggestions above are really __good improvements__ for the `MD` file that I worked at. Therefore, I accepted the suggestions and update the `MD` file based on their ideas.

__Finally__, I combined all the improvements I made and all the suggestions from other friendly contributors together to make the final `PR`.

Fortunately, the owner of the repository __accepted my PR__ and `merged` it to the main repository __in a short time__!

###My Feelings
This is an __interesting__ contribution. I'm really __happy__ that I can help to improve the documentation in the repository that belongs to my College. Also, I realized that __making contributions with other people__ is a very good way. Because _other people would see what you've missed at the first time_. And sometimes that could be a _small issue_, but sometimes that could be a __huge issue__. 
And no matter what, having someone else to help contributing on `Github` is always a __good thing__!

Link to the origin Repo I worked:[  [IPC144](https://github.com/Seneca-ICTOER/IPC144)  ]