[openoffice-project] branch main updated: Small correction

[ms...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

mseidel pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/openoffice-project.git


The following commit(s) were added to refs/heads/main by this push:
     new 8a59fde  Small correction
8a59fde is described below

commit 8a59fdeee9b1bc97e4e637e68be4d6a9099f0fc6
Author: mseidel <ms...@apache.org>
AuthorDate: Thu Jan 6 13:58:37 2022 +0100

    Small correction
---
 content/developer-faqs.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/developer-faqs.md b/content/developer-faqs.md
index 7e29428..9ebc1a3 100644
--- a/content/developer-faqs.md
+++ b/content/developer-faqs.md
@@ -76,7 +76,7 @@ e.g. issue 1234 is to use a #i1234# at the start of the commit message summary.
 Developer builds are not official releases and may be unstable. But they can be useful to download for those who 
 need early access to builds, but who do not want to compile their own build. They are announced and discussed only on the development list, as they are not production builds. Apache OpenOffice currently has two types of development builds: those generated by buildbots, and those manually generated/built.
 
-Apache OpenOffice makes use of buildbots for some of our environments. You can review the Apache OpenOffice buildbot information [here][16]. Additional information on buildbot builds for Windows, Linux64 can be found [here][13].
+Apache OpenOffice makes use of buildbots for some of our environments. You can review the Apache OpenOffice buildbot information [here][16]. Additional information on buildbot builds for Windows and Linux64 can be found [here][13].
 
 Development snapshots, which are manually generated, are used as the final step leading up to a release. These are used for final testing before an approved release. You will also find helpful hints for specific platform building here.