Fix rephrasing errors in the License profile and Contributing.md

Contributing.md

@@ -21,7 +21,7 @@ Once alerted, the SPDX tech group will review and provide feedback. Once profile
 This method of development was agreed upon by the SPDX Tech team on 2023-01-17.
 
 ## Profile Maintainers
-In accordance with the development model described above, each profile has at least maintainer in charge of merging profile-specific changes to the profile working branch. To contribute to a specific profile, please open a PR to the profile-specific branch or reach out to the maintainer of the profile (noted below). Each profile also has their own weekly meeting time which can be found [here](https://github.com/spdx/meetings#sub-groups-for-specific-topics).
+In accordance with the development model described above, each profile has at least one maintainer in charge of merging profile-specific changes to the profile working branch. To contribute to a specific profile, please open a PR to the profile-specific branch or reach out to the maintainer of the profile (noted below). Each profile in active development phase also has their own weekly meeting time which can be found [here](https://github.com/spdx/meetings#sub-groups-for-specific-topics).
 
 | Profile | Maintainer(s) |
 | ----------- | ----------- |

model/ExpandedLicensing/Classes/DisjunctiveLicenseSet.md

@@ -5,7 +5,7 @@ SPDX-License-Identifier: Community-Spec-1.0
 ## Summary
 
 Portion of an AnyLicenseInfo representing a set of licensing information
-where only any one of the elements applies.
+where only one of the elements applies.
 
 ## Description
 

model/SimpleLicensing/Classes/LicenseExpression.md

@@ -10,7 +10,7 @@ An SPDX Element containing an SPDX license expression string.
 
 Often a single license can be used to represent the licensing terms of a source code or binary file, but there are situations where a single license identifier is not sufficient. A common example is when software is offered under a choice of one or more licenses (e.g., GPL-2.0-only OR BSD-3-Clause). Another example is when a set of licenses is needed to represent a binary program constructed by compiling and linking two (or more) different source files each governed by different licenses (e.g., LGPL-2.1-only AND BSD-3-Clause).
 
-SPDX License Expressions provide a way for one to construct expressions that more accurately represent the licensing terms typically found in open source software source code. A license expression could be a single license identifier found on the SPDX License List; a user defined license reference denoted by the LicenseRef-idString; a license identifier combined with an SPDX exception; or some combination of license identifiers, license references and exceptions constructed using a small set of defined operators (e.g., AND, OR, WITH and +). We provide the definition of what constitutes a valid an SPDX License Expression in this section.
+SPDX License Expressions provide a way for one to construct expressions that more accurately represent the licensing terms typically found in open source software source code. A license expression could be a single license identifier found on the SPDX License List; a user defined license reference denoted by the LicenseRef-idString; a license identifier combined with an SPDX exception; or some combination of license identifiers, license references and exceptions constructed using a small set of defined operators (e.g., AND, OR, WITH and +). We provide the definition of what constitutes a valid SPDX License Expression in this section.
 
 ## Metadata