Add part 2 of the redhat blog

Signed-off-by: Avinal Kumar <avinkuma@redhat.com>

content/blogs/final-evaluation.rst

@@ -44,7 +44,7 @@ GitHub Actions CI/CD
     :width: 350
 
 Since the FOSSology project moved on Github, it has used only the free Travis CI service for OSS projects. 
-At the time of writing the Travis CI has reduced its free tier CI services. GitHub Actions provides faster builds. Since GitHub Actions is a fully managed service by GitHub, we don’t need to know how to scale and operate the infrastructure to run it. 
+At the time of writing Travis CI has reduced its free tier CI services. GitHub Actions provides faster builds. Since GitHub Actions is a fully managed service by GitHub, we don’t need to know how to scale and operate the infrastructure to run it. 
 
 It is straightforward to use with GitHub because when we fork a repository, the actions automatically get forked. This allows you to test and build projects very efficiently and even run them closer to the developer. Also, you have readily available access to the GitHub API, making it more popular among developers.
 
@@ -205,8 +205,8 @@ Deliverables
     
 
 
-How it works and how to use it?
--------------------------------
+How does it work and how to use it?
+-----------------------------------
 
 .. raw:: html
 
@@ -252,7 +252,7 @@ Each agent is a complete CMake sub-project with its independent configuration fo
     └── CMakeLists.txt                  # FOSSology Top-level CMake configuration 
 
 
-The :code:`cmake` directory contains customized CMake modules and templates for FOSSology. This directory is required for all the operations. The general workflow of the new build system as well as how to use it as described below.
+The :code:`cmake` directory contains customized CMake modules and templates for FOSSology. This directory is required for all the operations. The general workflow of the new build system as well as how to use it is described below.
 
 1. Since the new build system is still in review. You must fork FOSSology and pull the `#2075 <https://github.com/fossology/fossology/pull/2075>`_ pull request branch. Once you are in FOSSology root, run these commands.
 
@@ -331,7 +331,7 @@ The :code:`cmake` directory contains customized CMake modules and templates for
         ninja install
 
 
-6. While testing has some issues, but most of the testing is working fine. For now, you must build and run any test from the FOSSology root directory only. You can choose to configure a single agent if you want to test one agent only. See :code:`ctest --help` for controlling test runs.
+6. While testing has some issues, most of the testing is working fine. For now, you must build and run any test from the FOSSology root directory only. You can choose to configure a single agent if you want to test one agent only. See :code:`ctest --help` for controlling test runs.
 
     .. code-block:: bash
 
@@ -380,13 +380,13 @@ Although the transition from Makefiles to CMake and Travis CI to GitHub Actions
 - Running tests locally may require switching to :code:`fossy` user.
 - While configured for testing, it may give permission errors.
 - Scheduler, Ununpack, and Delagent unit and functional tests are not working. I have added an issue `#2084 <https://github.com/fossology/fossology/issues/2084>`_ to track the progress on fixing these tests.
-- CMake doesn't generates uninstall targets. The closest thing to uninstall is `this snippet <https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#can-i-do-make-uninstall-with-cmake>`_. This will be later added to the FOSSology.
+- CMake doesn't generate uninstall targets. The closest thing to uninstall is `this snippet <https://gitlab.kitware.com/cmake/community/-/wikis/FAQ#can-i-do-make-uninstall-with-cmake>`_. This will be later added to the FOSSology.
 
 
 Challenges Faced
 ----------------
 
-While this whole project was challenging, some aspects of it were unforeseen and more challenging. When I decided to go on with this project I just had enough CMake knowledge to write a configuration for a very small project. I had never used CMake on this big scale. On the other side, the FOSSology community is largely unknown to CMake so for all of us it was learn, practice, and implement. With support from mentors, I was able to overcome this challenge with flying colors.
+While this whole project was challenging, some aspects of it were unforeseen and more challenging. When I decided to go on with this project I just had enough CMake knowledge to write a configuration for a very small project. I had never used CMake on this big scale. On the other side, the FOSSology community is largely unknown to CMake so for all of us it was learned, practiced, and implement. With support from mentors, I was able to overcome this challenge with flying colors.
 
 The other challenge was to understand the old build system, how they are all connected and what is the flow. The complexity can be imagined by the fact that the most of code and configurations were written in the decade before the last decade and haven't changed much since then.
 
@@ -428,5 +428,5 @@ First of all, I want to thank and appreciate my mentors `Gaurav Mishra <https://
 
 I want to thank my friend and :abbr:`fellow participant (Integrating ScanCode Toolkit to FOSSology)` `Sarita <https://github.com/itssingh>`_. Thank you for being a collaborator, support, and motivation for attempting GSoC. 
 
-Finally, I want to thanks, my family and friends. I got to meet many awesome developers as my fellow participants from around the world, I wish we will do more collaboration in the future.
+Finally, I want to thank, my family and friends. I got to meet many awesome developers as my fellow participants from around the world, I wish we will do more collaboration in the future.
 

content/blogs/hrt-interview-1.rst

@@ -6,7 +6,7 @@
 :tags: HRT, hudsonrivertrading, interview, internship
 :slug: hrt-interview-1
 :category: blog
-:summary: I applied for **Systems Internship - Summer 2021** back in December 2020 at `Hudson River Trading <https://www.hudsonrivertrading.com>`_ , New York....Questions were clear and of medium level. But they were designed in such a way that you must know the basics before you could attempt.
+:summary: I applied for **Systems Internship - Summer 2021** back in December 2020 at `Hudson River Trading <https://www.hudsonrivertrading.com>`_ , New York.....Questions were clear and of medium level. But they were designed in such a way that you must know the basics before you could attempt.
 
 I applied for **Systems Internship - Summer 2021** back in December 2020 at `Hudson River Trading <https://www.hudsonrivertrading.com>`_ , New York. The internship description was: -
 
@@ -24,9 +24,8 @@ I applied for **Systems Internship - Summer 2021** back in December 2020 at `Hud
     * Data Storage
     * Large deployment or config management
 
-The first step was a coding test on Codility platform. If you have used any of the online coding platforms, this is similar. It was a 
-:abbr:`2.5 hrs (90 mins)` test consisting of 3 questions. They let you use :abbr:`online references (documentation, man pages etc.)` but 
-**do not copy the code** as it will highly reduce your chances of qualifying this first stage. You can choose between **C/C++**, 
+The first step was a coding test on the Codility platform. If you have used any of the online coding platforms, this is similar. It was a :abbr:`2.5 hrs (90 mins)` test consisting of 3 questions. They let you use :abbr:`online references (documentation, man pages, etc.)` but 
+**do not copy the code** as it will highly reduce your chances of qualifying for this first stage. You can choose between **C/C++**, 
 **Python** and **Golang** (no Java 😪). 
 
 Questions were clear and of medium level. But they were designed in such a way that you must know the basics before you could attempt. 
@@ -38,28 +37,28 @@ Also, they expected a clear and concise approach. Two of the most important poin
     * Please understand that this test is meant to be challenging. A perfect score is not necessary to move on to future interview rounds, so do the best you can!
 
 
-So, you must be near perfect in your approach as well as on time. I did them kind of quickly. They will show you a summery about your 
+So, you must be near perfect in your approach as well as on time. I did them kind of quickly. They will show you a summary of your 
 submission but not the results. It will take almost 2 weeks to get back to you for further steps.
 
 Next, I received a mail invitation for a telephonic interview. **This interview will last about 45 minutes and will be technical but will not require coding. Interview topics may include your background, programming languages, and Unix/Linux concepts**. Once you receive this 
-mail you can then decide a time slot for interview. 
+mail you can then decide a time slot for an interview. 
 
 I was not sure what they will ask if this is not a coding interview. The interviewer was very polite, and he was explaining the questions 
 too. Questions were not so tricky but practical and real-life. Since it was **not for SDE role**, the questions were mostly related to 
 Linux/Unix, C++ (mainly pointers and memory), Python/Bash scripting, automation, knowledge of tools (IDEs, Editors, System Administration 
 Tools) and previous experiences. The interview would often explain why he is asking this question, this was very nice. Then some common 
-interview questions, why you want to work for this role? What makes you fit for this role? etc. 
+interview questions, why do you want to work for this role? What makes you fit for this role? etc. 
 
 One thing that I want to point out is that the interviewer was repeatedly checking my resume, and for the most part he did not ask 
 anything that was not on my resume. So, my tip is to create a nice resume with genuine work/tool experiences. And when you are applying 
-for such role, it would be helpful if you mention mathematics or other courses that you have taken. *Do not lie on your resume*. They 
+for such a role, it would be helpful if you mention mathematics or other courses that you have taken. *Do not lie on your resume*. They 
 will easily catch that. 
 
 The other thing is to keep your words short and clear; I was not great at communication, but you can be. If the interviewer allows then 
-use examples for the things you cannot explain. I used nice examples. At last, he gave me a short feedback of how well I performed. 
+use examples for the things you cannot explain. I used nice examples. At last, he gave me short feedback on how well I performed. 
 
 At last, I want to point out things I should not have done. The first is, I did not ask much about the role, you must do this at least 
-once. Second, I am talkative, I do not know if interviewer was not faking his expressions (because he would often discuss in depth), 
-but not all interviewers will be same. So, do not talk too much, neither too less. At last work on your communication skill, mostly how 
-you present things and how to answer technical as well as behavioral questions. I was not fluent, but my way of presentation might 
+once. Second, I am talkative, I do not know if the interviewer was not faking his expressions (because he would often discuss in-depth), 
+but not all interviewers will be the same. So, do not talk too much, nor too less. At last work on your communication skill, mostly how 
+you to present things and how to answer technical as well as behavioral questions. I was not fluent, but my way of presentation might 
 have saved me.