Adding a new use case - fix syntax issues #255
Merged
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
The Jupyter Notebooks, along with their respective scopes, have been added to the Resources section.
I modified the presentation of the authors by adding their titles, affiliations, and contact information.
reasons: #113 (review)
3 spaces does not trigger indentation in most Markdown parsers. Use 2 space, 4 spaces, or a tab. 4 spaces or tab are most reliable.
wesleyboar
changed the title
3 tasks
Not doing ensures consistent space around nested lists.
Before: 1. Content was not part of each list item. 2. One list was intepreted as many. After: 1. Content is part of each list item. 2. One list has 6 items.
- Apparantly[^1], double spaces at end of line allows new line. - New lines help legibility, so use consistently for **Output/s:** [^1]: This for new line, instead of `<br>`, is new to me.
These instances of spaces: - do not effect syntax - seem to not have purpose
Closed
wesleyboar
added a commit
that referenced
this pull request
Dec 11, 2025
## What Did You Change? _On behalf of @nbonfante:_ > […] adding a New Use Case > — #251 ## Do You Want Support (syntax, design, etc)? - [x] Verify changes matches those of #251. - [x] Create a new PR to fix problems, #255. - [x] Show fixes to @nbonfante so as to teach. ## Any Reference Material Worth Sharing? Fixes merge conflict with #251, whose edits began on v2, but PR was made to v3. --------- Co-authored-by: nbonfante <nbonfante2023@my.fit.edu> Co-authored-by: Seb <sebabedin@gmail.com>
Base automatically changed from
nbonfante-main-v3-merge-conflict-resolved
to
main
December 11, 2025 21:31
✅ Deploy Preview for ds-user-guide ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
wesleyboar
deleted the
nbonfante-main-v3-merge-conflict-resolved--fixes
branch
wesleyboar
added a commit
that referenced
this pull request
Dec 11, 2025
Similar to cleanup done in #255.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What Did You Change?
Do You Want Support (syntax, design, etc)?
I present to @nbonfante, to guide future contributions.
Preview: deploy-preview-255--ds-user-guide.netlify.app
Any Reference Material Worth Sharing?
Fixes issues found in #251 / #252.