message: docs(models-with-same-name): change to be more readable
diff: @@ -5,27 +5,31 @@ title: 'Models with same name'
  This Guide shows all the possibilities for a model to use different names.
  -**Note**: if you want classes with the same name, you need to use one of these methods, so Typegoose can differentiate between them.
  +:::note
  +If Classes with the same name are wanted, these methods need to be used so that Typegooes can differentiate between them
  +:::
  ## SchemaOptions collection
  For this to work, `{ options: { automaticName } }` must be true.
  `{ schemaOptions: { collection } }` can be used to set a custom collection a model should use.
  +Using `{ schemaOptions: { collection } }` with `automaticName` automatically adds a suffix of the collection to the model's name.
  -Example:
  +Example without `automaticName`:
  ```ts
  @modelOptions({ schemaOptions: { collection: 'Something' } })
  class MultiModel {}
  const model = getModelForClass(MultiModel);
  +expect(model.modelName).to.be.equal('MultiModel');
  ```
  -Please note that using `{ schemaOptions: { collection } }` automatically adds a suffix of the collection to the model's name.
  +Example with `automaticName`:
  ```ts
  -@modelOptions({ schemaOptions: { collection: 'Something' } })
  +@modelOptions({ schemaOptions: { collection: 'Something' }, options: { automaticName: true } })
  class MultiModel {}
  const model = getModelForClass(MultiModel);
  @@ -46,7 +50,7 @@ const model = getModelForClass(CustomNameOption);
  expect(model.modelName).to.be.equal('CustomName');
  ```
  -If `{ options: { customName } }` is used with `{ options: { automaticName: true } }`, then it will be used as a _suffix_ of the normal name.
  +If `{ options: { customName } }` is used with `{ options: { automaticName: true } }`, then it will be used as a *suffix* of the normal name.
  Example:
  