docs/guide/structure-models.md - typo fixed [ci skip]

close #5847
This commit is contained in:
Nobuo Kihara
2014-11-01 18:49:10 +09:00
committed by Carsten Brandt
parent 9dcfd350ee
commit decf61a4f3

View File

@ -493,7 +493,7 @@ In summary, models
You may usually consider the last recommendation above when you are developing large complex systems. You may usually consider the last recommendation above when you are developing large complex systems.
In these systems, models could be very fat because they are used in many places and may thus contain many sets In these systems, models could be very fat because they are used in many places and may thus contain many sets
of rules and business logic. This often ends up in a nightmare in maintaining the model code of rules and business logic. This often ends up in a nightmare in maintaining the model code
because a single touch of the code could affect several different places. To make the mode code more maintainable, because a single touch of the code could affect several different places. To make the model code more maintainable,
you may take the following strategy: you may take the following strategy:
* Define a set of base model classes that are shared by different [applications](structure-applications.md) or * Define a set of base model classes that are shared by different [applications](structure-applications.md) or