Francis giovanni patch 10 #27
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Changes: "skils" to "skills" "thinkiing" to "thinking" "how it relates" to "how does it relate" Added commas after "systems" and "way" "behaviors" to "behaviours" (British English spelling)
Update Computational_Thinking.md
fix spacing
Update Computational_Thinking.md
Changes: "clarified" to "clarify" "in saying" to "by saying" "repsented" to "represented" "general statements" to "general statement" "skills is" to "skills are" "who wants to be a programmers" to "who want to be programmers" "skills" to "skill" "point of few" to "point of view" "emphatise" to "empathises" Removed extra space before "thinking skills" "and in a specific way" to "in a specific way" "with any other" to "from any other" Added a hyphen in "problem solving" to "problem-solving" "generalization" to "generalisation" (British English spelling) "modularizing" to "modularising" (British English spelling) Added a comma after "recursive" to maintain parallel structure. "thinkings" to "thinking" "abreviated" to "abbreviated" "later" to "latter" "This notes" to "These notes" Added "set of" before "four main components" Added a comma after "simplicity" Added "the" before "Python programming language"
Update Computational_Thinking.md
Changed "operator as another primitive abstraction concept of a computation" to an operator as another primitive abstraction concept of a computation. Changed "every computation may take in output and produce output" to every computation may take an input and produce an output. Changed "first evaluates the variable reference steps and get its value" to first evaluates the variable reference steps and gets its value. Changed "operators are convenient way" to operators are a convenient way. Changed "No programmers can ever written a code without debugging it" to No programmers have ever written code without debugging it. Changed "maybe we can write a print Hello World code without debugging it" to maybe we can write a print "Hello World" code without debugging it. Changed "requires programmers to test its code" to requires programmers to test their code. Changed "runs as what it is expected it to do" to runs as expected. Changed "the end of writing a long lines of code" to the end of writing long lines of code. Changed "programmers do test their code in bite-size" to programmers test their code in bite-size pieces. Changed "part and puzzle" to part and parcel. Changed "novice programmers" to novice programmer. Changed "one or few lines of code" to one or a few lines of code. Changed "performs what it is expected to do" to performs as expected. Changed "We will put here the final version" to We will put the final version here. Changed "novice programmers" to novice programmer. Changed "what are our input" to what our inputs. Changed "input to our computations and we know the output" to inputs to our computations are and we know the output. Changed "different way" to different ways. Added a comma after "but for simplicity". Removed extra space in "comments for". Added the before "Python keyword". Changed "functin" to function. Changed "Python expect" to Python expects. Changed "after every statement that ends with the colon :" to after every statement that ends with a colon :. Changed "value value" to computed value. Changed "commented the other function calls" to commented out the other function calls. Changed "remove the comment now and test" to remove the comments now and test them. Changed "calculate it using your calculator" to calculate the expected output using your calculator. Changed "test for the various input arguments and using" to test for the various input arguments using. Changed "test your code in bite-size" to test your code in bite-size pieces.
Update Basic_Operators.md
Corrections: Changed "computation is" to "computations are" for subject-verb agreement and plural consistency. Added a comma after "matters" for clarity and proper sentence flow. Replaced "if we can" with "whether we can" for formal phrasing. Added "the" before PCDIT for correct article usage. Changed "is" to "are" for subject-verb agreement with "steps." Changed "cycling cadence to hit" to "cycling cadence" for clarity. Changed "If the user hit" to "If the user hits" for tense consistency. Changed "IF" to lowercase "If" for proper formatting. Replaced "to set a lower target" with "suggest setting a lower target" for grammatical accuracy. Changed "encourage him" to "encourages them" for gender-neutral language. Replaced "the difference that the user's cadence average with the target" with "the difference between the user's cadence average and the target" for clarity and proper phrasing. Changed "to have a lower target" to "to set a lower target" for natural phrasing. Added a comma before "and in the process" for sentence flow. Changed "ask what is the input" to "ask about the input" for grammatical accuracy. Added commas for clarity in "input, output**,** and the computation process." Changed "the kind of data of the input and output" to "the kind of data used for the input and output" for clarity. Rephrased "a list of cadence of the user" to "a list of the user's cadence" for smoother phrasing. Added "about" in "ask further what is the data type" to "ask further about the data type." Adjusted "rotations per minute" formatting for clarity. Changed "the program, however, will end up in several possible states." to "the program, however, will end up in several possible states:" to introduce the list properly. Corrected capitalization for "state 1," "state 2," and "state 3" to "State 1," "State 2," and "State 3." Rephrased "compliment and reward user" to "compliments and rewards the user." Changed "he or she wants to modify" to "the option to modify" for concise phrasing. Replaced "has compute" with "must compute." Added a comma after "In the above" for clarity: "In the above,** we use..."** Corrected "talk about list" to "talk about lists" for grammatical agreement. Changed "just take not" to "just take note" for accuracy. Adjusted "some of the elements are not integer" to "some of the elements are not integers" for plural consistency. Added "The" before "PCDIT framework" for proper sentence structure: "The PCDIT framework..." Inserted "that" after "In the case" to make the sentence flow naturally: "In the case that we realize..." Changed "using" to "writing" for clarity: "Let's start with writing the pseudocode." Replaced "in such a way that" with "so that" for conciseness: "...general enough so that it can..." Modified "to think through about" to "think through" for smoother phrasing: "...to help us think through the steps..." Added a comma before "which" for proper punctuation: "...English for our pseudocode,** which we..."** Corrected "key words" to "keywords" to reflect the standard usage. Changed "helps" to "help" to agree with the plural subject "keywords." Changed "we introduced to you" to "we introduced" for smoother phrasing. Added a colon after "structures" for clarity: "...the three basic structures: sequential, branch,** and iterative."** Inserted "is" to complete the sentence structure: "...the branch structure is the one..." Added commas for readability: "...branch structure is the one that creates flexibility in our computer programs,** as it allows..."** and "...based on the branch structure,** as it chooses..."** Changed "certain block" to "a certain block" for proper article usage. Replaced "introduce" with "introduced" for past tense consistency. Added "an" before "algorithm" to correct grammar: "...iterate over your design of an algorithm..."
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.