Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Doc] Fix some incorrect uses of a/an #89444

Merged
merged 1 commit into from
Mar 13, 2024

Conversation

AThousandShips
Copy link
Member

Treating "LOD" as being pronounced "eLODee", otherwise this is largely fixing cases spelled correctly elsewhere

@AThousandShips AThousandShips added bug documentation cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release cherrypick:4.2 Considered for cherry-picking into a future 4.2.x release labels Mar 13, 2024
@AThousandShips AThousandShips added this to the 4.3 milestone Mar 13, 2024
@AThousandShips AThousandShips requested review from a team as code owners March 13, 2024 13:09
@@ -124,7 +124,7 @@
<param index="0" name="nd_threshold" type="float" />
<param index="1" name="target_index_count" type="int" default="3" />
<description>
Generates a LOD for a given [param nd_threshold] in linear units (square root of quadric error metric), using at most [param target_index_count] indices.
Generates an LOD for a given [param nd_threshold] in linear units (square root of quadric error metric), using at most [param target_index_count] indices.
Copy link
Member

Choose a reason for hiding this comment

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

I would say "lod" as a word, but I guess "el oh dee" is a valid form too.
Only "reference" I could find from a quick search is this shady looking https://www.spellchecker.net/lod

Copy link
Member Author

Choose a reason for hiding this comment

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

I'll restore too, though I'd read it as an acronym

Copy link
Member

Choose a reason for hiding this comment

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

Well I'm not sure on that one, might be worth polling on #rendering to see what folks are used to hearing :)

Copy link
Member Author

Choose a reason for hiding this comment

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

Given the current trend for the poll I added back the "LOD" cases, will squash or drop depending

Copy link
Member

Choose a reason for hiding this comment

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

I think you can go ahead and squash :)

@@ -1099,14 +1099,14 @@
<method name="rid_allocate_id">
<return type="int" />
<description>
Allocates a unique ID which can be used by the implementation to construct a RID. This is used mainly from native extensions to implement servers.
Copy link
Contributor

Choose a reason for hiding this comment

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

This does not feel right, can you elaborate on what I missed?

I would replace all of these RID over the place with a direct reference to the RID, but that's for later.

It feels so wrong to me I came back to this message just to try to wrap my head around it. To me, RID reads as it is written. And the acronym stands for "Resource Identifier", not "Identifier Resource".

Copy link
Member Author

@AThousandShips AThousandShips Mar 13, 2024

Choose a reason for hiding this comment

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

It's "ar I dee", not "rid", this isn't about anything else than grammar, the article just depends on if it proceeds a vowel sounds or not

@akien-mga akien-mga merged commit da945ce into godotengine:master Mar 13, 2024
16 checks passed
@akien-mga
Copy link
Member

Thanks!

@AThousandShips AThousandShips deleted the article_fix branch March 13, 2024 21:36
@AThousandShips
Copy link
Member Author

Thank you!

@akien-mga akien-mga removed cherrypick:4.1 Considered for cherry-picking into a future 4.1.x release cherrypick:4.2 Considered for cherry-picking into a future 4.2.x release labels Apr 8, 2024
@akien-mga akien-mga mentioned this pull request Jun 20, 2024
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants