Merge pull request #696 from euconnor/issue-666

Issue 666 - move file, other minor updates

Author: euconnor

common-requests/use.md

@@ -4,7 +4,7 @@ years: 2020 - 2026
 layout: page
 title: "How to use Open Horizon"
 description: "Basic instructions and examples for using the Open Horizon projects CLI"
-lastupdated: 2026-03-27
+lastupdated: 2026-03-30
 parent: Quick Start
 nav_order: 2
 ---
@@ -133,7 +133,7 @@ After you see the `agreement_execution_start_time` value, you can run `docker ps
 
 To use the exchange communication commands, set up two environment variables.
 
-### Pre-requisite
+### Prerequisite
 
 You need information from the All-in-One installation summary message that was displayed when you installed the {{site.data.keyword.mgmt_hub}}, agent, and CLI. This message begins with `----------- Summary of what was done:` and includes several generated passwords and tokens.
 
@@ -144,7 +144,7 @@ export HZN_ORG_ID=myorg
 export HZN_EXCHANGE_USER_AUTH=admin:[User org admin user generated password]
 ```
 
-> Now, you should be able to connect to the exchange with the CLI.
+Now, you can connect to the exchange by using the CLI.
 
 Use `hzn exchange status` or `hzn exchange node list` to confirm that it works with no errors. Additionally, `hzn exchange user list` displays the user account that you are currently using and if it is authenticated successfully.
 

docs/getting_started/faq.md

@@ -3,7 +3,7 @@ copyright: Contributors to the Open Horizon project
 years: 2020 - 2026
 title: FAQs
 description: Documentation for Frequently asked questions
-lastupdated: 2026-03-27
+lastupdated: 2026-03-30
 nav_order: 1
 parent: Help and Support
 ---
@@ -43,7 +43,7 @@ The following are answers to some frequently asked questions (FAQs) about {{site
 
 You can install the open source {{site.data.keyword.mgmt_hub}} (without the {{site.data.keyword.ieam}} management console) with the All-in-One installer for developers. The All-in-One installer creates a complete but minimal {{site.data.keyword.mgmt_hub}}, not suitable for production use. It also configures an example edge node. This tool enables open source component developers to get started quickly without the time it takes to configure a complete production {{site.data.keyword.ieam}} {{site.data.keyword.mgmt_hub}}. For information about the All-in-One installer, see [{{site.data.keyword.ieam}} - Devops ](https://github.com/open-horizon/devops/tree/master/mgmt-hub){:target="_blank"}{: .externalLink} GitHub repository.
 
-The All-in-One installer publishes a default set of example services during deployment. You can customize which sample services are published by setting the `BYO_SAMPLES` environment variable to point to a text file containing GitHub URLs of your own service repositories. This enables you to test and develop with your own custom services in addition to the default examples. For detailed instructions, see the [Using Custom Sample Services ](https://github.com/open-horizon/devops/tree/master/mgmt-hub#using-custom-samples){:target="_blank"}{: .externalLink} section in the {{site.data.keyword.mgmt_hub}} documentation.
+The All-in-One installer publishes a default set of sample services during deployment. You can customize which sample services are published by setting the `BYO_SAMPLES` environment variable to point to a text file that contains GitHub URLs of your own service repositories. This enables you to test and develop with your own custom services in addition to the default samples. For detailed instructions, see the [Using Custom Sample Services](../hub/custom_samples.md).
 
 ## Is {{site.data.keyword.ieam}} software open-sourced?
 {: #open_sourced}

common-requests/custom-samples.md docs/hub/custom_samples.mdcommon-requests/custom-samples.md renamed to docs/hub/custom_samples.md

@@ -4,18 +4,20 @@ years: 2026
 layout: page
 title: "Using custom sample services"
 description: "How to publish your own sample services with the All-in-One Management Hub"
-lastupdated: 2026-03-27
+lastupdated: 2026-03-30
 parent: Quick Start
 nav_order: 3
+parent: Installing Management hub
+grand_parent: Management Hub
 ---
 
 # Using custom sample services
 
-The {{site.data.keyword.ieam}} All-in-One {{site.data.keyword.mgmt_hub}} deployment includes a set of default example services that demonstrate edge computing capabilities. You can extend this by publishing your own custom sample services during the deployment process.
+The {{site.data.keyword.ieam}} All-in-One {{site.data.keyword.mgmt_hub}} deployment includes a set of default sample services that demonstrate edge computing capabilities. You can extend this by publishing your own custom sample services during the deployment process.
 
 ## Overview
 
-The Bring Your Own (BYO) Samples feature allows you to specify additional service repositories that are published to the Exchange during the All-in-One deployment. This is useful for:
+You can specify additional service repositories that are published to the Exchange during the All-in-One deployment. This is useful for:
 
 - Testing your own edge services in a development environment
 - Demonstrating custom solutions to stakeholders
@@ -31,7 +33,7 @@ When you set the `BYO_SAMPLES` environment variable, the deployment script:
 3. Publishes the service definition, service policy, and deployment policy to the Exchange
 4. Makes the services available for deployment to edge nodes
 
-Your custom samples are published in addition to the default {{site.data.keyword.ieam}} example services (CPU, GPS, and Hello World).
+Your custom samples are published in addition to the default {{site.data.keyword.ieam}} sample services (CPU, GPS, and Hello World).
 
 ## Prerequisites
 
@@ -42,13 +44,13 @@ Before using custom samples, ensure that:
   - `publish-service`: Publishes the service definition
   - `publish-service-policy`: Publishes the service policy
   - `publish-deployment-policy`: Publishes the deployment policy
-- Services are compatible with your target edge node architecture (AMD64, ARM, etc.)
+- Services are compatible with your target edge node architecture (AMD64, ARM, and so on.)
 
 ## Step-by-step instructions
 
 ### 1. Create a samples file
 
-Create a text file containing the GitHub URLs of your service repositories, one per line:
+Create a text file that contains the GitHub URLs of your service repositories. Each URL must be on a separate line. For example:
 
 ```text
 https://github.com/open-horizon/open-horizon-services/tree/main/web-helloworld-python
@@ -57,27 +59,27 @@ https://github.com/your-organization/another-service
 ```
 {: codeblock}
 
-Save this file (for example, as `my-samples.txt`) in a location accessible during deployment.
+Save this file (for example, as `samples.txt`) in a location that is accessible during deployment.
 
 ### 2. Set the environment variable
 
-Before running the deployment script, export the `BYO_SAMPLES` variable:
+Before you run the deployment script, export the `BYO_SAMPLES` variable:
 
 ```bash
-export BYO_SAMPLES=my-samples.txt
+export BYO_SAMPLES=samples.txt
 ```
 {: codeblock}
 
 ### 3. Run the deployment
 
-Run the All-in-One deployment script as usual:
+Run the All-in-One deployment script:
 
 ```bash
 curl -sSL https://raw.githubusercontent.com/open-horizon/devops/master/mgmt-hub/deploy-mgmt-hub.sh | bash
 ```
 {: codeblock}
 
-The script automatically detects the `BYO_SAMPLES` variable and publishes your custom services along with the default examples.
+The script automatically detects the `BYO_SAMPLES` variable and publishes your custom services with the default samples.
 
 ### 4. Verify the deployment
 
@@ -90,9 +92,9 @@ hzn exchange service list
 ```
 {: codeblock}
 
-You should see your custom services listed along with the default IBM examples.
+Verify that your custom services are listed along with the default samples.
 
-## Example service repository structure
+## Sample service repository structure
 
 Your service repository must follow this structure:
 
@@ -109,4 +111,4 @@ your-service/
     └── ... (your service code)
 ```
 
-The Makefile must include the `publish-only` target that calls the individual publish targets.
+The Makefile must include the `publish-only` target that calls the individual publish targets.