content suggestions

[jekennedy]

03_lesson/01_part/description.md

1. I suggest reworking the initial paragraph like so:
   Using Sails, existing services can be combined into a new, unified service. This is achieved by using the extends argument within the #[service] attribute. For example, imagine two services: Service A and Service B. A new service, Service C, can be created that incorporates features from both Service A and Service B, as if they were originally designed to be part of a single service.
2. Creating a new VftService struct containing BaseVftService as a field extends the standard fungible token service. > The VftService struct does not automatically “extend” the functionality of BaseVftService simply by containing it as a field.
3. It also includes a new method for creating a new instance of VftService. > It also includes a new method which initializes VftService using the default constructor of BaseVftService without any parameters.
4. Service attribute typos: The docs shows this: #[service(extends = BaseVftService, but the code shows: #[gservice(extends = VftService
5. This allows VftService to utilize methods from BaseVftService. > Implementing AsRef allows easy access to the inner BaseVftService when needed, but it doesn’t directly relate to utilizing methods from BaseVftService within VftService. The methods can be directly accessed through the vft field without needing AsRef.