From 76a8515dc064379e640e23224d17e731cb012543 Mon Sep 17 00:00:00 2001
From: shettygururaj <gururaj.shetty@huawei.com>
Date: Tue, 18 May 2021 14:00:22 +0530
Subject: [PATCH] docs: OpenHarmony changed to All scenarios OS

Some existence of OpenHarmony changed to All Scenarios OS in Readme
and Contribution files
This fixes #55, fixes #71

Signed-off-by: shettygururaj <gururaj.shetty@huawei.com>
---
 CONTRIBUTING.md                           | 2 +-
 README.md                                 | 2 +-
 docs/allscenarios-quick-build.rst         | 2 +-
 docs/build-flavours/zephyr-flavour.rst    | 2 +-
 docs/index.rst                            | 4 ++--
 meta-ohos-acts/README.md                  | 2 +-
 meta-ohos-core/README.md                  | 2 +-
 meta-ohos-core/classes/ohos-image.bbclass | 2 +-
 8 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 69d9d0d8..f926bac2 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -19,7 +19,7 @@ SPDX-License-Identifier: CC-BY-4.0
 
 ## Overview
 
-OpenHarmony project handles contributions as [merge requests](https://docs.gitlab.com/ee/user/project/merge_requests/) to relevant repositories part of the OpenHarmony [GitLab instance](https://git.ostc-eu.org/OSTC/OHOS). The flow for handling that is classic: fork-based merge requests. This means that once you have an account, you can fork any repository, create a branch with proposed changes and raise a merge request against the forked repository. More generic information you can find on the Gitlab's documentation as part of ["Merge requests workflow"](https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html).
+All Scenarios OS project handles contributions as [merge requests](https://docs.gitlab.com/ee/user/project/merge_requests/) to relevant repositories part of the All Scenarios OS [GitLab instance](https://git.ostc-eu.org/OSTC/OHOS). The flow for handling that is classic: fork-based merge requests. This means that once you have an account, you can fork any repository, create a branch with proposed changes and raise a merge request against the forked repository. More generic information you can find on the Gitlab's documentation as part of ["Merge requests workflow"](https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html).
 
 # REUSE compliance
 
diff --git a/README.md b/README.md
index bafbee42..c5de030c 100644
--- a/README.md
+++ b/README.md
@@ -7,7 +7,7 @@ SPDX-License-Identifier: CC-BY-4.0
 # meta-ohos
 
 **meta-ohos** is a collection of bitbake layers that implement the build system
-support in OpenHarmony. The build system documentation is available in the
+support in All Scenarios OS. The build system documentation is available in the
 `docs` subdirectory.
 
 ## Contributing
diff --git a/docs/allscenarios-quick-build.rst b/docs/allscenarios-quick-build.rst
index 2f93b1cc..fb619325 100644
--- a/docs/allscenarios-quick-build.rst
+++ b/docs/allscenarios-quick-build.rst
@@ -64,7 +64,7 @@ cloned using the repo tool. See above.
 
 .. Note::
 
-   Depending on the configuration type, a single OpenHarmony build could 
+   Depending on the configuration type, a single All Scenarios OS build could 
    use around 100GB of disk space for downloads, temporary files, and build artifacts combined.
 
 Initialize the build directory and run a build:
diff --git a/docs/build-flavours/zephyr-flavour.rst b/docs/build-flavours/zephyr-flavour.rst
index 6d2025f2..1f6250e3 100644
--- a/docs/build-flavours/zephyr-flavour.rst
+++ b/docs/build-flavours/zephyr-flavour.rst
@@ -7,7 +7,7 @@
 Zephyr Kernel Build Flavour
 ###########################
 
-OpenHarmony Zephyr build flavour is based on *allscenarios-zephyr* distribution (distro configuration).
+All Scenarios OS Zephyr build flavour is based on *allscenarios-zephyr* distribution (distro configuration).
 
 Supported images:
 
diff --git a/docs/index.rst b/docs/index.rst
index c0b83a04..1448459f 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -2,8 +2,8 @@
 ..
 .. SPDX-License-Identifier: CC-BY-4.0
 
-Build system documentation
-##########################
+Build System Guide
+##################
 
 .. toctree::
    :maxdepth: 1
diff --git a/meta-ohos-acts/README.md b/meta-ohos-acts/README.md
index 11f68bc6..faebc81b 100644
--- a/meta-ohos-acts/README.md
+++ b/meta-ohos-acts/README.md
@@ -31,6 +31,6 @@ Run 'bitbake-layers add-layer <path to meta-ohos>/meta-ohos-acts'
 ## Misc
 
 This layer builds a subset of the ACTS (Application Compatibility Test Suite)
-for Open Harmony OS. Some tests are not ported yet. Some tests are excluded
+for All Scenarios OS. Some tests are not ported yet. Some tests are excluded
 because they are duplicated in the greater bitbake ecosystem (e.g. LTP). Some
 tests are hardware or kernel specific and are not considered in this phase yet.
diff --git a/meta-ohos-core/README.md b/meta-ohos-core/README.md
index f3dbb2e7..fe53daa1 100644
--- a/meta-ohos-core/README.md
+++ b/meta-ohos-core/README.md
@@ -37,4 +37,4 @@ Run 'bitbake-layers add-layer /path/to/meta-ohos-core'
 III. Misc
 =========
 
-This layer provides recipes for the core elements of the OpenHarmony distribution.
+This layer provides recipes for the core elements of the All Scenarios OS distribution.
diff --git a/meta-ohos-core/classes/ohos-image.bbclass b/meta-ohos-core/classes/ohos-image.bbclass
index 349de172..535b2f98 100644
--- a/meta-ohos-core/classes/ohos-image.bbclass
+++ b/meta-ohos-core/classes/ohos-image.bbclass
@@ -2,7 +2,7 @@
 #
 # SPDX-License-Identifier: Apache-2.0
 
-# OpenHarmony functionality for images
+# All Scenarios OS functionality for images
 
 # List of tty to mask getty for
 SYSTEMD_MASK_GETTY ?= ""
-- 
GitLab