Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug🐛: Remove "Intel" from the phrase "Intel FDO" #513

Closed
joewxboy opened this issue Aug 3, 2023 · 4 comments
Closed

Bug🐛: Remove "Intel" from the phrase "Intel FDO" #513

joewxboy opened this issue Aug 3, 2023 · 4 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@joewxboy
Copy link
Member

joewxboy commented Aug 3, 2023

Describe the bug.

On https://open-horizon.github.io/docs/installing/fdo/ and possibly other pages, the FDO project is referred to as "Intel FDO". This is incorrect, and the FDO project has requested that we change it to read merely "FDO" instead.

Describe the steps to reproduce the behavior

No response

Expected behavior.

No response

Screenshots.

No response

Operating environment

n/a

Additional context

No response

@joewxboy joewxboy added bug Something isn't working good first issue Good for newcomers labels Aug 3, 2023
@johnwalicki
Copy link
Member

There are also references of Intel in https://github.com/open-horizon/FDO-support README

@johnwalicki
Copy link
Member

The correct technique to fix this issue is to make edits in the FDO-support repo. There is a CopyDocs GHA that will copy the markdown files here.

FWIW, the incorrectly placed docs/fdo/*.md files should be deleted. The live files are in docs/fdo/docs dir (via the GHA)

@joewxboy
Copy link
Member Author

Submitted this PR: open-horizon/FDO-support#47

@joewxboy
Copy link
Member Author

Fixed by PR, closing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working good first issue Good for newcomers
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants