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

@@ -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
 

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

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:

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:
 

docs/index.rst

@@ -2,8 +2,8 @@
 ..
 .. SPDX-License-Identifier: CC-BY-4.0
 
-Build system documentation
-##########################
+Build System Guide
+##################
 
 .. toctree::
    :maxdepth: 1

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.

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.

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 ?= ""