chore: cleanup readme

- updated license and copyright

Author: mrdav30

.gitattributes

@@ -4,7 +4,7 @@
 # Declare files that will always have LF line endings on checkout.
 *.sh text eol=lf
 
-# Don't check these into the repo as LF to work around TeamCity bug
+# Don't check these into the repo as LF normalization will mess with them.
 *.xml     -text
 *.targets -text
 

CONTRIBUTING.md

@@ -1,36 +1,25 @@
 # Contributing
 
-When contributing to this repository, please first discuss the change you wish to make via issue,
-email, or any other method with the owners of this repository before making a change. 
+When contributing to this repository, please first discuss the change you wish to make via issue, email, or any other method with the owners of this repository before making a change.
 
 Please note we have a code of conduct, please follow it in all your interactions with the project.
 
 ## Pull Request Process
 
-1. Ensure any install or build dependencies are removed before the end of the layer when doing a 
-   build.
-2. Update the README.md with details of changes to the interface, this includes new environment 
-   variables, exposed ports, useful file locations and container parameters.
-3. Increase the version numbers in any examples files and the README.md to the new version that this
-   Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
-4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you 
-   do not have permission to do that, you may request the second reviewer to merge it for you.
+1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
+2. Update the README.md with details of changes to the interface, this includes new environment variables, exposed ports, useful file locations and container parameters.
+3. Increase the version numbers in any examples files and the README.md to the new version that this Pull Request would represent. The versioning scheme we use is [SemVer](http://semver.org/).
+4. You may merge the Pull Request in once you have the sign-off of two other developers, or if you do not have permission to do that, you may request the second reviewer to merge it for you.
 
 ## Code of Conduct
 
 ### Our Pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
 
 ### Our Standards
 
-Examples of behavior that contributes to creating a positive environment
-include:
+Examples of behavior that contributes to creating a positive environment include:
 
 * Using welcoming and inclusive language
 * Being respectful of differing viewpoints and experiences
@@ -40,53 +29,31 @@ include:
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
+* The use of sexualized language or imagery and unwelcome sexual attention or advances
 * Trolling, insulting/derogatory comments, and personal or political attacks
 * Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
+* Publishing others' private information, such as a physical or electronic address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a professional setting
 
 ### Our Responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
 
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
 
 ### Scope
 
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
 
 ### Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at `david.oravsky@gmail.com`. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at `david.oravsky@gmail.com`. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
+Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
 
 ### Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [http://contributor-covenant.org/version/1/4][version]
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at [http://contributor-covenant.org/version/1/4][version]
 
 [homepage]: http://contributor-covenant.org
-[version]: http://contributor-covenant.org/version/1/4/
+[version]: http://contributor-covenant.org/version/1/4/

COPYRIGHT

@@ -0,0 +1,11 @@
+Copyright Information
+
+Primary Author
+David Oravsky (mrdav30)
+2024–present
+
+Contributors
+Additional contributors may be listed in the project's Git history.
+
+Unless otherwise stated, all source code in this repository is
+copyright the author and licensed under the MIT License.

LICENSE.md LICENSELICENSE.md renamed to LICENSE

@@ -1,6 +1,6 @@
 MIT License
 
-Copyright (c) 2024 mrdav30
+Copyright (c) 2024–present David Oravsky (mrdav30)
 
 Permission is hereby granted, free of charge, to any person obtaining a copy
 of this software and associated documentation files (the "Software"), to deal
@@ -18,4 +18,4 @@ FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
 AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
 LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
 OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
-SOFTWARE.
+SOFTWARE.

NOTICE

@@ -0,0 +1,30 @@
+Additional Terms and Notices
+
+Copyright (c) 2024–present David Oravsky (mrdav30)
+
+1. Project Names and Branding
+
+The names "FixedMathSharp"
+and related branding are the property of the original author.
+
+These names may not be used to promote, endorse, or sell derived works
+without prior written permission from the author.
+
+2. Redistribution
+
+Redistribution of this software, whether modified or unmodified, must
+include the original LICENSE and NOTICE files.
+
+3. Standalone Resale
+
+This project may not be redistributed or sold as a standalone development
+toolkit, framework, or asset package without explicit permission from the
+author.
+
+This restriction does not prevent use of the software as part of a larger
+application, game, engine, or commercial product.
+
+4. Attribution
+
+Derived works must retain attribution to the original project and author
+in documentation or repository history.

README.md

@@ -1,4 +1,5 @@
-FixedMathSharp
+# FixedMathSharp
+
 ==============
 
 ![FixedMathSharp Icon](https://raw.githubusercontent.com/mrdav30/fixedmathsharp/main/icon.png)
@@ -12,7 +13,7 @@ Ideal for simulations, games, and physics engines requiring reliable arithmetic
 
 ## 🛠️ Key Features
 
-- **Deterministic Calculations:** Ensures consistent results across different platforms. 
+- **Deterministic Calculations:** Ensures consistent results across different platforms.
 - **High Precision Arithmetic:** Uses fixed-point math to eliminate floating-point inaccuracies.
 - **Comprehensive Vector Support:** Includes 2D and 3D vector operations (`Vector2d`, `Vector3d`).
 - **Quaternion Rotations:** Leverage `FixedQuaternion` for smooth rotations without gimbal lock.
@@ -26,21 +27,20 @@ Ideal for simulations, games, and physics engines requiring reliable arithmetic
 
 ## 🚀 Installation
 
-
 Clone the repository and add it to your project:
 
 ### Non-Unity Projects
 
 1. **Install via NuGet**:
    - Add FixedMathSharp to your project using the following command:
-   
+
      ```bash
      dotnet add package FixedMathSharp
      ```
 
 2. **Or Download/Clone**:
    - Clone the repository or download the source code.
-   
+
      ```bash
      git clone https://github.com/mrdav30/FixedMathSharp.git
      ```
@@ -59,31 +59,35 @@ FixedMathSharp is now maintained as a separate Unity package.For Unity-specific
 
 ## 📖 Usage Examples
 
-### Basic Arithmetic with `Fixed64`:
+### Basic Arithmetic with `Fixed64`
+
 ```csharp
 Fixed64 a = new Fixed64(1.5);
 Fixed64 b = new Fixed64(2.5);
 Fixed64 result = a + b;
 Console.WriteLine(result); // Output: 4.0
 ```
 
-### Vector Operations:
+### Vector Operations
+
 ```csharp
 Vector3d v1 = new Vector3d(1, 2, 3);
 Vector3d v2 = new Vector3d(4, 5, 6);
 Fixed64 dotProduct = Vector3d.Dot(v1, v2);
 Console.WriteLine(dotProduct); // Output: 32
 ```
 
-### Quaternion Rotation:
+### Quaternion Rotation
+
 ```csharp
 FixedQuaternion rotation = FixedQuaternion.FromAxisAngle(Vector3d.Up, FixedMath.PiOver2); // 90 degrees around Y-axis
 Vector3d point = new Vector3d(1, 0, 0);
 Vector3d rotatedPoint = rotation.Rotate(point);
 Console.WriteLine(rotatedPoint); // Output: (0, 0, -1)
 ```
 
-### Matrix Transformations:
+### Matrix Transformations
+
 ```csharp
 Fixed4x4 matrix = Fixed4x4.Identity;
 Vector3d position = new Vector3d(1, 2, 3);
@@ -92,14 +96,16 @@ Console.WriteLine(matrix);
 ```
 
 ### Bounding Shapes and Intersection
+
 ```csharp
 BoundingBox box = new BoundingBox(new Vector3d(0, 0, 0), new Vector3d(5, 5, 5));
 BoundingSphere sphere = new BoundingSphere(new Vector3d(3, 3, 3), new Fixed64(1));
 bool intersects = box.Intersects(sphere);
 Console.WriteLine(intersects); // Output: True
 ```
 
-### Trigonometry Example:
+### Trigonometry Example
+
 ```csharp
 Fixed64 angle = FixedMath.PiOver4; // 45 degrees
 Fixed64 sinValue = FixedTrigonometry.Sin(angle);
@@ -148,14 +154,15 @@ int loot = rngOre.Next(1, 5); // [1,5)
 
 ### Fixed64 Struct
 
-**Fixed64** is the core data type representing fixed-point numbers. It provides various mathematical operations, including addition, subtraction, multiplication, division, and more. 
+**Fixed64** is the core data type representing fixed-point numbers. It provides various mathematical operations, including addition, subtraction, multiplication, division, and more.
 The struct guarantees deterministic behavior by using integer-based arithmetic with a configurable `SHIFT_AMOUNT`.
 
 ---
 
 ## ⚡ Performance Considerations
 
 FixedMathSharp is optimized for high-performance deterministic calculations:
+
 - **Inline methods and bit-shifting optimizations** ensure minimal overhead.
 - **Eliminates floating-point drift**, making it ideal for lockstep simulations.
 - **Supports fuzzy equality comparisons** for handling minor precision deviations.
@@ -164,10 +171,11 @@ FixedMathSharp is optimized for high-performance deterministic calculations:
 
 ## 🧪 Testing and Validation
 
-Unit tests are used extensively to validate the correctness of mathematical operations. 
+Unit tests are used extensively to validate the correctness of mathematical operations.
 Special **fuzzy comparisons** are employed where small precision discrepancies might occur, mimicking floating-point behavior.
 
 To run the tests:
+
 ```bash
 dotnet test --configuration debug
 ```
@@ -187,10 +195,6 @@ dotnet test --configuration debug
 
 We welcome contributions! Please see our [CONTRIBUTING](https://github.com/mrdav30/FixedMathSharp/blob/main/CONTRIBUTING.md) guide for details on how to propose changes, report issues, and interact with the community.
 
-## 📄 License
-
-This project is licensed under the MIT License - see the [LICENSE](https://github.com/mrdav30/FixedMathSharp/blob/main/LICENSE.md) for details.
-
 ---
 
 ## 👥 Contributors
@@ -211,3 +215,13 @@ For bug reports or feature requests, please open an issue in this repository.
 We welcome feedback, contributors, and community discussion across all projects.
 
 ---
+
+## License
+
+This project is licensed under the MIT License.
+
+See the following files for details:
+
+- LICENSE – standard MIT license
+- NOTICE – additional terms regarding project branding and redistribution
+- COPYRIGHT – authorship information