# Codebook: Classical Factorization

**URL:** <https://discuss.pennylane.ai/t/codebook-classical-factorization/4987>\
**Category:** Codebook\
**Created:** [July 29, 2024, 7:15pm UTC](https://discuss.pennylane.ai/t/codebook-classical-factorization/4987 "2024-07-29T19:15:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![CatalinaAlbornoz](https://yyz2.discourse-cdn.com/flex012/user_avatar/discuss.pennylane.ai/catalinaalbornoz/32/1196_2.png) [@CatalinaAlbornoz](https://discuss.pennylane.ai/u/CatalinaAlbornoz)\
**Post date:** [July 29, 2024, 7:15pm UTC](https://discuss.pennylane.ai/t/codebook-classical-factorization/4987/1 "2024-07-29T19:15:51Z")

</div>

Ask here about the [“Classical Factorization” Codebook topic](https://pennylane.ai/codebook/10-shors-algorithm/02-classical-factorization/) from the “Shor’s Algorithm” module.

---

<div class="post-metadata">

**Author:** ![jhanschoo](https://yyz2.discourse-cdn.com/flex012/user_avatar/discuss.pennylane.ai/jhanschoo/32/2890_2.png) [@jhanschoo](https://discuss.pennylane.ai/u/jhanschoo)\
**Post date:** [January 31, 2025, 6:35am UTC](https://discuss.pennylane.ai/t/codebook-classical-factorization/4987/2 "2025-01-31T06:35:03Z")

</div>

The text and code in this section says “nontrivial square root of m” and “nontrivial square root modulo m” interchangeably to mean the same thing. I would like it if all such terminology was standardized to “nontrivial square root modulo m”.

Reason being that they are frequently referred to more precisely as “nontrivial square roots of unity modulo m”, and they aren’t square roots of m in the usual sense that their square is m; rather, their square is 1.

---

<div class="post-metadata">

**Author:** ![CatalinaAlbornoz](https://yyz2.discourse-cdn.com/flex012/user_avatar/discuss.pennylane.ai/catalinaalbornoz/32/1196_2.png) [@CatalinaAlbornoz](https://discuss.pennylane.ai/u/CatalinaAlbornoz)\
**Post date:** [January 31, 2025, 10:49pm UTC](https://discuss.pennylane.ai/t/codebook-classical-factorization/4987/3 "2025-01-31T22:49:47Z")

</div>

Thanks for this feedback @jhanschoo ! I agree your suggestion can help avoid confusion.
