New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unclear instruction: Learn String Manipulation by Building a Cypher Step 3 #54234
Comments
Hi @samGreer I do not see the word "parentheses" used twice, I hope I understood the issue correctly. |
If I understood correctly you mean the parentheses in |
The only parentheses I can see on second paragraph are the following:
If I understood correctly, right? @samGreer If so, these are just used syntactically, so they should be ignored |
Hi @zairahira, thanks for the questions. By "parentheses", I mean the symbols "(" and ")", not the word. Apologies for the confusion. My proposed solution would be rewriting the second paragraph as follows: Functions are reusable code blocks that you can call/run/invoke when you need them. To call a function, you just need to write a pair of parentheses next to its name. You will learn more about functions very soon. My issue with the previous was that the use of parentheses in the paragraph previously indicated to me examples of syntax, while not actually being examples of syntax. I think this rewriting clears up that confusion, and means that parentheses are used in this step during examples of function calls, which I think reads clearer |
Okay, I had missed the first sentence of your post @samGreer . I would go with:
|
Thanks for the clearification @samGreer 👍️ |
Describe the Issue
The second paragraph of the instructions (shown below) uses parentheses twice.
Given that this is a lesson about the syntax for how to call a function, I think the use of parentheses is confusing
Affected Page
https://www.freecodecamp.org/learn/scientific-computing-with-python/learn-string-manipulation-by-building-a-cipher/step-3
Your code
N/A (not a coding issue)
Expected behavior
N/A (not a coding issue)
Screenshots
No response
System
Additional context
No response
The text was updated successfully, but these errors were encountered: