Update how-to-create-vector-index.md
Clarifying that the Index type is Registered Index which lets you select the one created above. The statement left a gap where if you selected FAISS having previously selected FAISS to create the vector database.
@2good4hisowngood : Thanks for your contribution! The author(s) have been notified to review your proposed change.
Learn Build status updates of commit be4ac4a:
:white_check_mark: Validation status: passed
| File | Status | Preview URL | Details |
|---|---|---|---|
| articles/machine-learning/how-to-create-vector-index.md | :white_check_mark:Succeeded |
For more details, please refer to the build report.
For any questions, please:
- Try searching the learn.microsoft.com contributor guides
- Post your question in the Learn support channel
@balapv
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged" @MicrosoftDocs/public-repo-pr-review-team
@balapv
Can you review this old PR and determine whether it needs to be closed or merged?
@MicrosoftDocs/public-repo-pr-review-team
#sign-off
Invalid command: '#sign-off'. Only the assigned author of one or more file in this PR can sign off. @balapv
@court72 I am the docs reviewer on this article and I accepted the change. Can this be merged please? Thank you!
Thank you for contributing to this Azure documentation. Unfortunately, changes to Machine Learning content can't be accepted this week. The Skilling Content group is migrating this content to a new repository: azure-ai-docs.
In the meantime, we are closing this PR and tagging it so that when the content is available in the new repo, we can follow up with new location information.
#label:"migrate-followup" #please-close
@2good4hisowngood We’re happy to share that contributions to machine-learning, ai-studio, ai-services, genomics, open-datasets, search are once again possible at azure-ai-docs. We appreciated your patience during this migration.
Find your article in the new repository and make the changes there (or copy/paste the raw markdown from your changed file) and open a new PR.
#remove-label:"migrate-followup"