Skip to content

docs: fix 7 typos and grammar errors in comments and documentation - #121

Closed
Avicennasis wants to merge 2 commits into
rust-lang:masterfrom
Avicennasis:docs/fix-typos
Closed

Avicennasis wants to merge 2 commits into
rust-lang:masterfrom
Avicennasis:docs/fix-typos

Conversation

@Avicennasis

Copy link
Copy Markdown

Summary

Fix 7 typos and grammar errors across 2 files.

vision/status_quo/nalgebra.md

  • R` and `C` represents the number` → RandC represent the number
  • // For matrices of know size.// For matrices of known size.
  • /// A matrix of statically know size./// A matrix of statically known size.
  • backwards compatability concernbackwards compatibility concern
  • by going to back to typenum → `by going back to `typenum
  • By adding one trait impl impl forBy adding one trait impl for

meetings/2021.02.09-lazy-norm.md

  • * additional weirdness`` → * additional weirdness`

Otherwise comments, documentation and message strings only — no functional changes.

@teor2345 teor2345 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we're going to fix typos, let's fix these ones as well.

These fixes are all correct, but they might not be accepted under the internal documentation typo policy:
https://rustc-dev-guide.rust-lang.org/building/compiler-documenting.html#contributing-documentation

View changes since this review

Comment thread vision/status_quo/nalgebra.md Outdated
}
```
While this can be avoided by going to back to `typenum` and using associated types, this adds a lot of unnecessary bounds and inpacts all of the code dealing with it.
While this can be avoided by going back to `typenum` and using associated types, this adds a lot of unnecessary bounds and inpacts all of the code dealing with it.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whoops, missed a typo

Suggested change
While this can be avoided by going back to `typenum` and using associated types, this adds a lot of unnecessary bounds and inpacts all of the code dealing with it.
While this can be avoided by going back to `typenum` and using associated types, this adds a lot of unnecessary bounds and impacts all of the code dealing with it.

Comment thread vision/status_quo/nalgebra.md Outdated
*a huge thanks to [Andreas Borgen Longva](https://github.com/Andlon) and [Sébastien Crozet](https://github.com/sebcrozet) for the help with figuring this out*

[nalgebra](https://nalgebra.org/) is a linear algebra library. At the core of that library is a type `struct Matrix<T, R, C, S>` where `T` is the components scalar type, `R` and `C` represents the number of rows and columns and `S` represents the type of the buffer containing the data.
[nalgebra](https://nalgebra.org/) is a linear algebra library. At the core of that library is a type `struct Matrix<T, R, C, S>` where `T` is the components scalar type, `R` and `C` represent the number of rows and columns and `S` represents the type of the buffer containing the data.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Missed this one too

Suggested change
[nalgebra](https://nalgebra.org/) is a linear algebra library. At the core of that library is a type `struct Matrix<T, R, C, S>` where `T` is the components scalar type, `R` and `C` represent the number of rows and columns and `S` represents the type of the buffer containing the data.
[nalgebra](https://nalgebra.org/) is a linear algebra library. At the core of that library is a type `struct Matrix<T, R, C, S>` where `T` is the components' scalar type, `R` and `C` represent the number of rows and columns and `S` represents the type of the buffer containing the data.

Both from @teor2345's review of #121:
- components scalar type -> components' scalar type (missing possessive)
- inpacts -> impacts
@Avicennasis

This comment was marked as low quality.

@steffahn steffahn closed this Sep 18, 2026
@Jules-Bertholet

Jules-Bertholet commented Sep 19, 2026

Copy link
Copy Markdown

they might not be accepted under the internal documentation typo policy

Does that policy apply to this repo?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants