Merge pull request #239 from ansys/MB_26R1_RBD

MB - Rigid Body Dynamics Grammatical Updates

Author: AnsMelanie

2026R1/rigid-bd-26-r1/actuator.md

@@ -26,17 +26,17 @@ Measure that stores the energy generated by the actuator.
 ### Member functions
 
 There are two ways to define the value of the load: using a variable, or by
-defining a table of input measures (in which case a variable is defined
-automatically).
+defining a table of input measures, in which case a variable is defined
+automatically.
 
 `SetVariable(variable)`
 
 `variable` is a list of input measures in table form.
 
 `SetInputMeasure(measure)`
 
-`measure` is typically the time measure object, but other measures can be used
-as well. When using an expression to define a load variation, the measure must
+`measure` is typically the time measure object, but other measures can also 
+be used. When using an expression to define a load variation, the measure must
 have only one component (it cannot be a vector measure). The variation can be
 defined by a constant, an expression, or a table.
 
@@ -53,8 +53,8 @@ constant.
 `SetFunc(string, is_degree)`
 
 `string` is similar to the expression used in the user interface to define a
-joint condition by a function. Note that the literal variable is always called
-`time`, even if you are using another measure as input.
+joint condition using a function. Note that the literal variable is always
+called `time`, even if you are using another measure as input.
 
-`is_degree` is a boolean argument. If the expression uses trigonometric
+`is_degree` is a boolean argument. If the expression uses a trigonometric
 function, it specifies that the input variable should be expressed in degrees.

2026R1/rigid-bd-26-r1/basis.md

@@ -15,4 +15,4 @@ ID table: `CS_Basis`
 
 double [,]`Matrix`
 
-Sets or gets function of the transformation matrix
+Sets or gets function of the transformation matrix.

2026R1/rigid-bd-26-r1/body.md

@@ -27,7 +27,7 @@ Name of the body.
 
 Origin Coordinate System of the body. This Coordinate System is the moving
 coordinate system of one of the joints connected to the body. The choice of
-this joint, called parent joint, is the result of an optimization that
+this joint, known as the parent joint, is the result of an optimization that
 minimizes the number of degrees of freedom of the system.
 
 `InertiaBodyCoordinateSystem`
@@ -60,13 +60,13 @@ CS_Variable Iyy, CS_Variable Izz)`
 
 Overwrites the constant mass and principal inertia properties by variable
 properties. During the solution process, the mass and inertia variation rate
-needs to be evaluated. Therefore, only Point Table, Polynomial and Function
+must be evaluated. Therefore, only Point Table, Polynomial and Function
 can be used to define the variation. Python user tables cannot be used to
-define kinetic properties variations. You can make some of the properties
+define kinetic property variations. You can make some of the properties
 (mass, Ixx, Iyy and Izz) constants by using constant variables.
 
 **Note**
-The principal axis needs to be defined when the principal inertia is being
+The principal axis must be defined when the principal inertia is being
 assigned. If the body is created by a command,
 `SetCenterOfMassAndOrientationAngles` or `SetCenterOfMassAndOrientationMatrix`
 must be called before calling `SetVariableMassAndPrincipalInertia`.  
@@ -75,11 +75,11 @@ This function only applies to rigid bodies.
 
 **Note**
 All quantities used in the solver must use a consistent unit system, which
-sometimes differs from the user interface unit system. For example if the user
-interface unit system is "mm,kg,N,s", the solver unit system will be
+sometimes differs from the user interface unit system. For example, if the
+user interface unit system is "mm,kg,N,s", the solver unit system will be
 "mm,t,N,s". When using `SetMassAndInertia` or
-`SetVariableMassAndPrincipalInertia`, the values of mass and inertia have to
-be entered using the solver unit system.  
+`SetVariableMassAndPrincipalInertia`, the values of mass and inertia must
+be entered using the solver unit system.
 
 ### Derived classes
 

2026R1/rigid-bd-26-r1/bodycoordinatesystem.md

@@ -21,10 +21,10 @@ ID table: `CS_BodyCoordinateSystem`
 `RotateArrayThroughTimeToLocal(MeasureValues)`
 
 Rotates the transient values of a measure to a coordinate system.
-`MeasureValues` is a python two-dimensional array, such as that coming out of
+`MeasureValues` is a python two-dimensional array, such as that returned by
 `FillValuesThroughTime` or `FillDerivativesThroughTime`. This function works
 for 3D vectors such as relative translation between two coordinate systems or
-6-D vectors such as forces/moments.
+6D vectors such as forces/moments.
 
 `RotateArrayThroughTimeToGlobal(MeasureValues)`
 

2026R1/rigid-bd-26-r1/breakable-joint.md

@@ -32,7 +32,7 @@ breakable joint:
     ```
 
     Next, make the driver only active if the force in the joint is less than a
-    maximum threshold of 3N. To do that, create a [Condition](condition.md) based on the joint
+    maximum threshold of 3N. To do this, create a [Condition](condition.md) based on the joint
     force measure norm.
 
 5. Retrieve the force on the joint:

2026R1/rigid-bd-26-r1/changelog.md

@@ -1,5 +1,5 @@
 # Changelog
 
-## Version 2025 R2
+## Version 2026 R1
 
-- No changes in this release.
+- General grammatical updates.

2026R1/rigid-bd-26-r1/constraint-equation.md

@@ -53,9 +53,8 @@ commands is shown below. A description of these commands follows.
     ```
 
     The first argument is the joint object. The second argument defines the DOF
-    (degrees of freedom) of the joint that are involved in the relation. Here, `0`
-    represents the rotation, which is the joint's first and only DOF is the
-    rotation.
+    (degrees of freedom) of the joints that are involved in the relation. Here, `0`
+    represents the rotation, which is the joint's first and only DOF.
 
 5. The second term and right hand side are introduced in the same manner:
 

2026R1/rigid-bd-26-r1/contact.md

@@ -6,8 +6,8 @@ Corresponding ID table: `CS_Contact`
 
 **Note**
 If multiple contact objects have been defined between the same two bodies
-(with different surfaces), the solver merges them into one single pair. In
-that case, only one of the contact pairs exists and the call to
+(using different surfaces), the solver merges them into a single pair. In
+this case, only one of the contact pairs exists and the call to
 `CS_Contact.Find(_cid)` will fail for all contact objects other than the one
 that was used to handle the pair of bodies.  
 

2026R1/rigid-bd-26-r1/contactdebugmask.md

@@ -1,9 +1,8 @@
 # ContactDebugMask
 
 The ContactDebugMask object allows you to activate and customize the output of
-contact points. It can also be used to modify the default behaviour of
-contact. ContactDebugMask uses a set of switches that can be toggled on or
-off.
+contact points. It can also be used to modify the default contact behaviour.
+ContactDebugMask uses a set of switches that can be toggled on or off.
 
 ID table: `CS_ContactDebugMask`
 

2026R1/rigid-bd-26-r1/contactoptions.md

@@ -12,7 +12,7 @@ None
 
 `TimeOut`
 
-Time in second (=30.0 by default)
+Time in seconds (=30.0 by default)
 
 `Verbose`