# Is there a way to merge those document fix and add it into next release ASAP?

**URL:** <https://forum.crystal-lang.org/t/is-there-a-way-to-merge-those-document-fix-and-add-it-into-next-release-asap/4949>\
**Category:** Crystal Contrib\
**Created:** [September 18, 2022, 4:50pm UTC](https://forum.crystal-lang.org/t/is-there-a-way-to-merge-those-document-fix-and-add-it-into-next-release-asap/4949 "2022-09-18T16:50:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![zw963](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/zw963/32/1623_2.png) [@zw963](https://forum.crystal-lang.org/u/zw963)\
**Post date:** [September 18, 2022, 4:50pm UTC](https://forum.crystal-lang.org/t/is-there-a-way-to-merge-those-document-fix-and-add-it-into-next-release-asap/4949/1 "2022-09-18T16:50:14Z")

</div>

e.g.

[Fix docs error for File.match? `**` globbing pattern. by zw963 · Pull Request #12343 · crystal-lang/crystal · GitHub](https://github.com/crystal-lang/crystal/pull/12343),

> <https://github.com/crystal-lang/crystal/pull/12492>

My concern is, those document fix never breaking anything, right? those a very simple changes, we can always release it safely, not worry about breaking something, probably we need a individual more efficient/simple CI process for those simple doc things instead.

We have a lot of documentation need additions/fixes/improvements, better documentation is better for newcomers, i really want to help, but the current process leaves me unmotivated.

* * *

Following is comment by @straight-shoota

> [@](#):
>
> Yes, this PR is a trivial fix and it should be fine to accept it without a second approval.
> 
> [#12343](https://github.com/crystal-lang/crystal/pull/12343) on the other hand is not as trivial and I think it’s important to vet such documentation changes, even if it won’t break any code.
> 
> It’s still a very simple change, so reviewing should be pretty quick. I do not know why no other Core Team member has approved it yet.
> 
> I understand that such a long process even for simple changes can be demotivating. I’d wish we could move faster. This is a discussion for another place, though. Let’s continue this on the forums.

---

<div class="post-metadata">

**Author:** ![asterite](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/asterite/32/60_2.png) [@asterite](https://forum.crystal-lang.org/u/asterite)\
**Post date:** [September 18, 2022, 5:06pm UTC](https://forum.crystal-lang.org/t/is-there-a-way-to-merge-those-document-fix-and-add-it-into-next-release-asap/4949/2 "2022-09-18T17:06:40Z")

</div>

The best way is to comment with ping on that issue. I follow the repo and I actually commented on the issue back then. But then I forgot. So all that’s needed is a ping. I or someone else will see that ping.

---

<div class="post-metadata">

**Author:** ![straight-shoota](https://yyz2.discourse-cdn.com/flex036/user_avatar/forum.crystal-lang.org/straight-shoota/32/36_2.png) [@straight-shoota](https://forum.crystal-lang.org/u/straight-shoota)\
**Post date:** [September 19, 2022, 8:54am UTC](https://forum.crystal-lang.org/t/is-there-a-way-to-merge-those-document-fix-and-add-it-into-next-release-asap/4949/3 "2022-09-19T08:54:43Z")

</div>

For reviewers, this link might be helpful to identify PRs that have already one approval from a Core Team member, so reviewing them would help to move them forward (low hanging fruit).

[https://github.com/pulls?q=is%3Apr+is%3Aopen+org%3Acrystal-lang+archived%3Afalse+sort%3Aupdated-desc+-reviewed-by%3A%40me+draft%3Afalse+-author%3A%40me+review%3Aapproved](https://github.com/pulls?q=is%3Apr+is%3Aopen+org%3Acrystal-lang+archived%3Afalse+sort%3Aupdated-desc+-reviewed-by%3A%40me+draft%3Afalse+-author%3A%40me+review%3Aapproved)