-
Notifications
You must be signed in to change notification settings - Fork 32
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
Improve readability and wording #172
base: main
Are you sure you want to change the base?
Improve readability and wording #172
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for taking the time to edit the documentation! However, in this case since "testscript" and "testcase" are in reference to internal classes they should be left as is.
@GerriorL @aitestino Similar as to was done here (but probably without adding the back ticks for inline code). |
I think that would be for the best |
@aitestino Apologies for the likely flood of GH emails. I started by using the webui code review feature and I really should have gone the distance and submit a pull request to you. (That's what I'm doing now as aitestino#1.) |
.. _Variable Scoping: https://docs.python.org/3.4/reference/executionmodel.html | ||
|
||
``aetest`` is a data-driven test infrastructure. Its scripts and testcases are | ||
``aetest`` is a data-driven test infrastructure. Its scripts and test cases are |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree with the change on this line.
Here this is not a code object, but instead a normal English noun.
* test case > Testcase * test script > TestScript
Update Testcase and TestScript in parameters.rst
@GerriorL |
Corrected typos, sentence structure, and overall added clarity.