Fix typos on course document

tanto259 · vargajb · tanto259 · commit 376f4934fe51 · 2022-12-13T22:20:51.000+08:00
Co-authored-by: Janos Varga &lt;113785741+vargajb@users.noreply.github.com&gt;
Signed-off-by: Hartanto Ario Widjaya &lt;tanto259@users.noreply.github.com&gt;
diff --git a/COBOL Programming Course #1 - Getting Started/README.md b/COBOL Programming Course #1 - Getting Started/README.md
@@ -23,7 +23,7 @@ These materials are being used by other organizations to provide COBOL training
 
 ## Build
 
-The PDF is built using the following [pandoc](https://pandoc.org/) command. Note: pdflatex is required. [MiKTeX](https://miktex.org/) can be installed to accomodate this. 
+The PDF is built using the following [pandoc](https://pandoc.org/) command. Note: pdflatex is required. [MiKTeX](https://miktex.org/) can be installed to accommodate this. 
 
 ```
 pandoc "COBOL Programming Course #1 - Getting Started.md" -o "COBOL Programming Course #1 - Getting Started.pdf" --number-sections --toc -B Front_Matter.tex --listings
diff --git a/COBOL Programming Course #2 - Learning COBOL/COBOL Programming Course #2 - Learning COBOL.md b/COBOL Programming Course #2 - Learning COBOL/COBOL Programming Course #2 - Learning COBOL.md
@@ -3472,8 +3472,8 @@ To read more on data sets, visit the IBM Knowledge Center:
 - S013-68: Block size is larger than 32752
 - S013-A4: SYSIN or SYSOUT is not QSAM file
 - S013-A8: Invalid record format for SYSIN or SYSOUT
-- S013-D0: Attemped to define PDS with FBS or FS record format
-- S013-E4: Attemped to concatenate more than 16 PDSs
+- S013-D0: Attempted to define PDS with FBS or FS record format
+- S013-E4: Attempted to concatenate more than 16 PDSs
 
 **Frequent Causes:**
 Most of the reason for this ABEND code is due to inconsistencies between the JCL and the COBOL program.
diff --git a/COBOL Programming Course #2 - Learning COBOL/README.md b/COBOL Programming Course #2 - Learning COBOL/README.md
@@ -23,7 +23,7 @@ These materials are being used by other organizations to provide COBOL training
 
 ## Build
 
-The PDF is built using the following [pandoc](https://pandoc.org/) command. Note: pdflatex is required. [MiKTeX](https://miktex.org/) can be installed to accomodate this. 
+The PDF is built using the following [pandoc](https://pandoc.org/) command. Note: pdflatex is required. [MiKTeX](https://miktex.org/) can be installed to accommodate this. 
 
 ```
 pandoc "COBOL Programming Course #2 - Learning COBOL.md" -o "COBOL Programming Course #2 - Learning COBOL.pdf" --number-sections --toc -B Front_Matter.tex --listings
diff --git a/COBOL Programming Course #3 - Advanced Topics/COBOL Programming Course #3 - Advanced Topics.md b/COBOL Programming Course #3 - Advanced Topics/COBOL Programming Course #3 - Advanced Topics.md
@@ -282,7 +282,7 @@ Let us consider a dynamic-length elementary item. To recall, an elementary item
 
 If the content received is longer than the current length, a new larger buffer will be allocated for it. Additionally, if the length of the sender is zero, the receiver's length will be set to zero as well.
 
-Now, if the dynamic-length elementary item is used to receive data and we reference-modified it, the item will be treated as a fixed-length item with with a length equals to the current length of the dynamic-length item. In such cases, the compiler will not allocate or reallocated the buffer.
+Now, if the dynamic-length elementary item is used to receive data and we reference-modified it, the item will be treated as a fixed-length item with a length equals to the current length of the dynamic-length item. In such cases, the compiler will not allocate or reallocated the buffer.
 
 Note that not all statement supports dynamic-length elementary items. Common statement like REDEFINE or RENAME will not work. Additionally, we cannot take their address using the ADDRESS-OF special register. The full list of the statements supported is available on the [Language Reference](https://www.ibm.com/docs/en/cobol-zos/6.4?topic=relationships-dynamic-length-items).
 
@@ -403,7 +403,7 @@ Business application solutions were architected decades ago using programming la
     - **Using VSCode and Zowe Explorer**
 
 ## Enterprise COBOL APIs
-IBM mainframe flagship operating system, z/OS, includes software that has enabled large scale business applications for decades.  The software is frequently referred to as 'middleware'. Examples of z/OS 'middleware' is Db2, a relational database, CICS, transactional processor, IMS, both transactional and hierarchical database, and MQSeries, a mechanism to store and forward data between systems asynchonously.
+IBM mainframe flagship operating system, z/OS, includes software that has enabled large scale business applications for decades.  The software is frequently referred to as 'middleware'. Examples of z/OS 'middleware' is Db2, a relational database, CICS, transactional processor, IMS, both transactional and hierarchical database, and MQSeries, a mechanism to store and forward data between systems asynchronously.
 
 ### z/OS Middleware
 A fundamental capability of z/OS middleware software is communication enablement of programming languages.  The z/OS middleware software includes documentation and examples of how any specific programming language can communicate with the specific z/OS middleware software.  A programming language, such as Enterprise COBOL, would use documented interfaces and techniques to initiate services and pass data between the COBOL application program and the middleware. 
@@ -492,7 +492,7 @@ Observe ":CUSTOMER-RECORD" in the EXEC SQL FETCH statement.  A colon (:) precede
 *Example 3. COBOL Data Item for storing variables where Db2 is the data source*
 
 ## SQL Capability within Enterprise COBOL
-Learning SQL is a separate technical skill.  The objective of this brief chapter is familiarization with Enterprise COBOL use of SQL API.  A COBOL program is capable of any SQL communication with Db2 for z/OS assuming necessary authority is granted.  SQL has four catagories as outlined in Example 4.  Learning SQL is necessary for a COBOL programmer to become proficient with using the Db2 API for a variety of possible applications where COBOL provides the what, how, and when logic of executing specific SQL.  
+Learning SQL is a separate technical skill.  The objective of this brief chapter is familiarization with Enterprise COBOL use of SQL API.  A COBOL program is capable of any SQL communication with Db2 for z/OS assuming necessary authority is granted.  SQL has four categories as outlined in Example 4.  Learning SQL is necessary for a COBOL programmer to become proficient with using the Db2 API for a variety of possible applications where COBOL provides the what, how, and when logic of executing specific SQL.  
 
 ```
 DDL - Data Definition Language
@@ -506,7 +506,7 @@ INSERT
 UPDATE
 DELETE 
 
-DCL - Data Control Langauge
+DCL - Data Control Language
 GRANT
 REVOKE
 
@@ -520,7 +520,7 @@ ROLLBACK
 Db2 for z/OS V12 is the most current release of Db2 at the moment.  The Db2 V12 for z/OS Application Programming and SQL Guide is available using internet search SC27-8845, the Db2 for z/OS professional manual number.  Db2 V12 for z/OS SQL Reference is also necessary to advance programming API capability (SC27-8859).
 
 ### Db2 Data Base Administration (DBA) vs Application Programming
-In large enterprise, the roles and responsibilities are divided for a number of reasons.  The responsibility of the DBA would include the DDL and DCL outlined in Example 4.  The DBA is responsibile for managing the entire relational data base environment to insure availability, security, performance, etc.  The system programmers and DBAs frequently setup the application development procedures for COBOL programmer development, testing, and maintenance of the COBOL business applications.  A COBOL application programmer is typically provided documented procedures to follow to apply their COBOL programming and SQL API expertise.
+In large enterprise, the roles and responsibilities are divided for a number of reasons.  The responsibility of the DBA would include the DDL and DCL outlined in Example 4.  The DBA is responsible for managing the entire relational data base environment to insure availability, security, performance, etc.  The system programmers and DBAs frequently setup the application development procedures for COBOL programmer development, testing, and maintenance of the COBOL business applications.  A COBOL application programmer is typically provided documented procedures to follow to apply their COBOL programming and SQL API expertise.
 
 Enterprise COBOL is a learning journey.  Each Enterprise COBOL API is a separate learning journey.  As is the case with most professional endeavors, learning, repetition, and applying what is learned is re-iterative process leading to advanced skill levels.
 
@@ -530,7 +530,7 @@ The lab contains data used in previous labs from "COBOL Programming Course #1 -
 The lab contains Enterprise COBOL source code with Db2 APIs along with the JCL to compile and execute the COBOL programs.
 
 ### Using VSCode and Zowe Explorer
-Zowe Explorer is currently without the ability to execute Db2 SQL interactively. It is inevitable Zowe Explorer will eventually have the capability of connectiong to relational databases and executing SQL.
+Zowe Explorer is currently without the ability to execute Db2 SQL interactively. It is inevitable Zowe Explorer will eventually have the capability of connecting to relational databases and executing SQL.
 
 Therefore, JCL members were created to create and load user tables following examples provided.
 
@@ -1123,7 +1123,7 @@ Clearly, Mari’s changes to the program that generates the reports have broken
 
 Can you fix the code to get the correct result? The new source code is named **CBL0106** and the JCL is **CBL0106J**. In case you get stuck, the solution is in the file **CBL0106C**. 
 
-You can find them in the github repository for the COBOL course, in the subfolder **/COBOL Programming Course #2 - Advanced Topics/Challenges/Debugging**.
+You can find them in the GitHub repository for the COBOL course, in the subfolder **/COBOL Programming Course #3 - Advanced Topics/Challenges/Debugging**.
 
 \newpage
 ## COBOL Challenge - The COVID-19 Reports
@@ -1294,7 +1294,7 @@ We will explore the popular Hacker News website for this challenge. Hacker News
 The site offers a dynamic list of posts/stories, submitted by users, each of which could be expanded into its own unique comment thread. Readers can upvote or downvote links and comments, and the top thirty links are featured on the front page. Today, more than five million people read Hacker News each month, and landing a blog post on the front page is a badge of honor for many technologists.
 
 ### Our Goal
-We will be working on a Hacker News 2015-2016 dataset from Kaggle with a full year’s worth of stories:  Our goal is to extract only the Mainframe/COBOL related stories and assign ranking scores to them based on (a simplified version) the published Hacker News ranking algorithm. We will create a front page report that reflects this ranking order. The algorithm works in a way that nothing stays on the front page for too long, so a story’s score will eventually drop to zero over time (the gravity effect). Since our posts are spread out over a year and as older posts will always have a lower (or zero) ranking, we will distort the data so all our stories have the same date and and consider only the times in the ranking score calculation. This will give all our posts a fair chance of landing the front page.  Our front page report is published at 11:59pm. [Here's some additional information on the ranking.](https://www.righto.com/2013/11/how-hacker-news-ranking-really-works.html)
+We will be working on a Hacker News 2015-2016 dataset from Kaggle with a full year’s worth of stories:  Our goal is to extract only the Mainframe/COBOL related stories and assign ranking scores to them based on (a simplified version) the published Hacker News ranking algorithm. We will create a front page report that reflects this ranking order. The algorithm works in a way that nothing stays on the front page for too long, so a story’s score will eventually drop to zero over time (the gravity effect). Since our posts are spread out over a year and as older posts will always have a lower (or zero) ranking, we will distort the data so all our stories have the same date and consider only the times in the ranking score calculation. This will give all our posts a fair chance of landing the front page.  Our front page report is published at 11:59pm. [Here's some additional information on the ranking.](https://www.righto.com/2013/11/how-hacker-news-ranking-really-works.html)
 
 ### The Plan
  - There are different creative ways of accomplishing this but here’s our plan: We will have a COBOL program that reads the input CSV file and retrieves only the ***Mainframe/COBOL*** stories. It then calculates the ranking score for the stories by factoring in the time they were posted and the number of votes they received. Each of the records is then written to an output dataset along with the ranking score. 
diff --git a/COBOL Programming Course #3 - Advanced Topics/README.md b/COBOL Programming Course #3 - Advanced Topics/README.md
@@ -16,7 +16,7 @@ These materials are being used by other organizations to provide COBOL training
 
 ## Build
 
-A PDF can be built using the following [pandoc](https://pandoc.org/) command. Note: pdflatex is required. [MiKTeX](https://miktex.org/) can be installed to accomodate this. Prior to issuing the following command, all subscript and superscript notation must be changed. Find all instances of `<sub>` and `<\sub>` and replace them with `~`. Find all instances of `<sup>` and `<\sup>` and replace them with `^`. This is the notation required for pandoc but this would make it difficult to read the markdown in GitHub.
+A PDF can be built using the following [pandoc](https://pandoc.org/) command. Note: pdflatex is required. [MiKTeX](https://miktex.org/) can be installed to accommodate this. Prior to issuing the following command, all subscript and superscript notation must be changed. Find all instances of `<sub>` and `<\sub>` and replace them with `~`. Find all instances of `<sup>` and `<\sup>` and replace them with `^`. This is the notation required for pandoc but this would make it difficult to read the markdown in GitHub.
 
 ```
 pandoc "COBOL Programming Course #3 - Advanced Topics.md" -o "COBOL Programming Course #3 - Advanced Topics.pdf" --number-sections --toc -B Front_Matter.tex --listings
diff --git a/COBOL Programming Course #4 - Testing/README.md b/COBOL Programming Course #4 - Testing/README.md
@@ -16,7 +16,7 @@ These materials are being used by other organizations to provide COBOL training
 
 ## Build
 
-A PDF can be built using the following [pandoc](https://pandoc.org/) command. Note: pdflatex is required. [MiKTeX](https://miktex.org/) can be installed to accomodate this. 
+A PDF can be built using the following [pandoc](https://pandoc.org/) command. Note: pdflatex is required. [MiKTeX](https://miktex.org/) can be installed to accommodate this. 
 
 ```
 pandoc "COBOL Programming Course #4 - Testing.md" -o "COBOL Programming Course #4 - Testing.pdf" --number-sections --toc --listings
