Fix incorrect return type documentation for m1_from_mc_m2 function

This commit corrects the documentation for the m1_from_mc_m2 function to accurately
reflect its behavior:

Update return value documentation to specify that the function always returns a
numpy.ndarray (even for scalar inputs)
Clarify that the return array will have the same shape as the input m2 parameter
if m2 is an array
Improve overall docstring clarity with more descriptive function summary and
parameter descriptions
Keep the actual function logic unchanged as it is working as intended

Author: tuhinbits

TOVsolver/solver_code.py

@@ -7,15 +7,20 @@
 
 
 def m1_from_mc_m2(mc, m2):
-    """a function that feed back the companion star mass from GW event measurement.
+    """Calculate companion star mass from chirp mass and one component mass
+    
+    Given the chirp mass from a gravitational wave event and one component mass,
+    calculate the other component mass.
 
     Args:
-        mc (float): chrip mass of a GW event, unit in solar mass.
-        m2 (float or numpy array): the determined mass for one of the star, this is computed from sampling of EoS.
+        mc (float): Chirp mass of a GW event, in solar mass units
+        m2 (float or numpy.ndarray): Mass of one component, in solar mass units
 
     Returns:
-        m1 (array): the companion star mass in solar mass.
+        numpy.ndarray: Mass of the companion star (m1), in solar mass units.
+            Will have the same shape as the input m2 if m2 is an array.
     """
+    
     m2 = np.array(m2)
     num1 = (2.0 / 3.0) ** (1.0 / 3.0) * mc**5.0
     denom1 = (