docs: typos (#1988)

Co-authored-by: cary hu <[email protected]>

Author: cary-hu

docs/docs/configuration/additional-mapping-parameters.mdx

@@ -62,7 +62,7 @@ but higher than a by-name matched regular member mapping.
 </Tabs>
 
 :::info
-Mappings with additional parameters do have some limitions:
+Mappings with additional parameters do have some limitations:
 
 - The additional parameters are not passed to nested mappings.
 - A mapping with additional mapping parameters cannot be the default mapping

docs/docs/configuration/analyzer-diagnostics/RMG060.mdx

@@ -45,7 +45,7 @@ in such cases.
     [Mapper]
     public partial class CarMapper
     {
-      public paratial List<CarDto> CarsToCarDtos(List<Car> cars);
+      public partial List<CarDto> CarsToCarDtos(List<Car> cars);
 
       // highlight-start
       [UserMapping(Default = true)]

docs/docs/configuration/constant-generated-values.mdx

@@ -56,7 +56,7 @@ This also works for constructor parameters.
 
 ### Named mapping
 
-The name of the value generator can be overriden by the `NamedMapping` attribute:
+The name of the value generator can be overridden by the `NamedMapping` attribute:
 
 ```csharp
 [MapValue(nameof(CarDto.SourceSystem), Use = "CustomGetSourceSystem")]

docs/docs/configuration/enum.mdx

@@ -115,7 +115,7 @@ are not affected by naming strategies.
 
 ## Manually mapped enum values
 
-To explicitly map enum values the `MapEnumValueAttibute` can be used.
+To explicitly map enum values the `MapEnumValueAttribute` can be used.
 Attribute is only valid on enum-to-enum, enum-to-string and string-to-enum mappings.
 
 Explicit enum mappings are not affected by enum naming strategies.
@@ -189,7 +189,7 @@ the `RequiredEnumMappingStrategy` can be used. By default this property will inh
 
         Sets the `RequiredEnumMappingStrategy` for all methods within the mapper,
         by default it is `Both` requiring all members to be mapped.
-        This can be overriden by individual mapping methods using `MapperRequiredMappingAttribute`.
+        This can be overridden by individual mapping methods using `MapperRequiredMappingAttribute`.
 
         ```csharp
         // highlight-start

docs/docs/configuration/external-mappings.mdx

@@ -31,7 +31,7 @@ In order for Mapperly to find the mappings, they must be made known with `UseMap
         public static class BananaMapper
         {
             public static Banana MapBanana(BananaDto dto)
-            => new Banana(dto.Weigth);
+            => new Banana(dto.Weight);
         }
         ```
 
@@ -55,7 +55,7 @@ In order for Mapperly to find the mappings, they must be made known with `UseMap
         public static class BananaMapper
         {
             public static Banana MapBanana(BananaDto dto)
-            => new Banana(dto.Weigth);
+            => new Banana(dto.Weight);
         }
         ```
 

docs/docs/configuration/mapper.mdx

@@ -156,7 +156,7 @@ or by setting the `IgnoreObsoleteMembersStrategy` option of the `MapperAttribute
 
         Sets the `IgnoreObsoleteMembersStrategy` for all methods within the mapper,
         by default it is `None` allowing obsolete source and target members to be mapped.
-        This can be overriden by individual mapping methods using `MapperIgnoreObsoleteMembersAttribute`.
+        This can be overridden by individual mapping methods using `MapperIgnoreObsoleteMembersAttribute`.
 
         ```csharp
         // highlight-start
@@ -259,7 +259,7 @@ the `RequiredMappingStrategy` can be used.
 
         Sets the `RequiredMappingStrategy` for all methods within the mapper,
         by default it is `Both` requiring all members to be mapped.
-        This can be overriden by individual mapping methods using `MapperRequiredMappingAttribute`.
+        This can be overridden by individual mapping methods using `MapperRequiredMappingAttribute`.
 
         ```csharp
         // highlight-start

docs/docs/configuration/private-members.mdx

@@ -96,7 +96,7 @@ This allows you to use inaccessible constructors but only map accessible members
 ## Controlling member accessibility
 
 In addition to mapping inaccessible members,
-`MemberVisbility` can be used to control which members are considered, depending on their accessibility modifier.
+`MemberVisibility` can be used to control which members are considered, depending on their accessibility modifier.
 For instance `MemberVisibility.Private | MemberVisibility.Protected` will cause Mapperly to only consider private and protected members,
 generating an unsafe accessor if needed.
 

docs/docs/configuration/user-implemented-methods.mdx

@@ -105,7 +105,7 @@ The mapper will respect the `ref` keyword on the target parameter when using an
   [Mapper(AllowNullPropertyAssignment = false, UseDeepCloning = true, RequiredMappingStrategy = RequiredMappingStrategy.Source)]
   public static partial class UseUserMethodWithRef
   {
-      [MapProperty(nameof(ArrayObject.IntArray), nameof(ArrayObject.IntArray), Use = nameof(MapArray))] // `Use` is required otheriwse it will generate it's own
+      [MapProperty(nameof(ArrayObject.IntArray), nameof(ArrayObject.IntArray), Use = nameof(MapArray))] // `Use` is required otherwise it will generate it's own
       public static partial void Merge([MappingTarget] ArrayObject target, ArrayObject second);
 
       private static void MapArray([MappingTarget] ref int[] target, int[] second) => target = [.. target, .. second.Except(target)];

docs/docs/contributing/debugging.md

@@ -13,7 +13,7 @@ Check [here](../configuration/generated-source.mdx) on how to inspect the genera
 ## Unit tests
 
 To debug the Mapperly in unit tests, set a breakpoint
-in the code of Mappery which you want to debug and run the tests in debug mode.
+in the code of Mapperly which you want to debug and run the tests in debug mode.
 
 ## Integration tests