fix typo in documentation from relationship attribute and all manipulation of back populate #579
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.
I notice a few typo in documentation,so i decided to fix it .
I detected these errors because we did not take into consideration the key concept of sqlmodel concerning the back populate
Here is the key concept
That tells SQLModel that if something changes in this model, it should change that attribute in the other model, and it will work even before committing with the session (that would force a refresh of the data).
Here is the comparison considering the key concept of sqlmodel .
Here is some images after considering the key concept
![after_back_relationship_01](https://user-images.githubusercontent
.com/37194177/230231651-6a8c8f2d-5fee-476a-b7d6-225d8eacc153.png)
Here is some images before considering the key concept