Updating doc links to TypeSpec.io & few broken anchor links (#352)

Author: allenjzhang

README.md

@@ -20,7 +20,7 @@ You can try TypeSpec on the web without installing anything.
 
 ## Getting Started
 
-For TypeSpec language documentation, see https://microsoft.github.io/typespec.
+For TypeSpec language documentation, see https://typespec.io/docs.
 
 If you are team working on Azure, see TypeSpec Azure development documentation https://azure.github.io/typespec-azure. You should pre-install as well `@azure-tools/typespec-azure-core` to define Azure resources, and `@azure-tools/typespec-autorest` to export in Swagger:
 

docs/emitters/typespec-autorest/index.md

@@ -74,7 +74,7 @@ or via the command line with
 
 #### `emitter-output-dir`
 
-Set the emitter output-dir. [See here](https://microsoft.github.io/typespec/introduction/configuration#emitter-output-dir)
+Set the emitter output-dir. [See here](https://typespec.io/docs/handbook/configuration#emitter-output-dir)
 
 #### `output-file`
 

docs/getstarted/azure-resource-manager/step00.md

@@ -2,7 +2,7 @@
 
 ## Installing IDE Tools
 
-If you use Visual Studio or Visual Studio code, the TypeSpec extensions are an important tool in providing a first class experience for writing, editing, and reviewing TypeSpec. See [Installing the VS and VS Code Extensions](https://microsoft.github.io/typespec/introduction/installation#install-the-vs-and-vscode-extensions) for details.
+If you use Visual Studio or Visual Studio code, the TypeSpec extensions are an important tool in providing a first class experience for writing, editing, and reviewing TypeSpec. See [Installing the VS and VS Code Extensions](https://typespec.io/docs#install-the-vs-and-vscode-extensions) for details.
 
 ## Creating a Service
 

docs/getstarted/azure-resource-manager/step02.md

@@ -6,7 +6,7 @@ There are three essential components of a resource defined with TypeSpec:
 
 - A model type representing the resource, derived from one of the [base resource types](#base-resource-types)
 - A model type defining the properties of the resource type
-- An interface that defines the operations that can be performed on the resource type, usually a combination of [standard resource operations](#standard-resource-operations) and [custom actions](#custom-actions)
+- An interface that defines the operations that can be performed on the resource type, usually a combination of [recommended and required Operations](../../howtos/ARM/resource-operations.md#recommended-and-required-operations) and [resource actions](../../howtos/ARM/resource-operations.md#resource-actions-post)
 
 > Read the [TypeSpec tutorial](https://github.com/Microsoft/typespec/blob/main/docs/tutorial.md) to learn the basics about TypeSpec model types and interfaces.
 

docs/getstarted/installation.md

@@ -9,7 +9,7 @@ You can try TypeSpec on the web without installing anything.
 
 ### Installing TypeSpec core toolset
 
-See https://microsoft.github.io/typespec/introduction/installation
+See https://typespec.io/docs
 
 ## Installing TypeSpec Azure toolsets
 

docs/howtos/Azure Core/content-negotiation.md

@@ -1,6 +1,6 @@
 # Content Type Negotiation
 
-See [Http documentation on content type negotiation](https://microsoft.github.io/typespec/next/standard-library/http/content-types#content-type-negotiation) for the general concept
+See [Http documentation on content type negotiation](https://typespec.io/docs/next/libraries/http/content-types#content-type-negotiation) for the general concept
 
 ## Usage with Azure.Core operations
 

docs/howtos/migrate-swagger/get-started.md

@@ -33,5 +33,5 @@ We have created a swagger to TypeSpec conversion tool to help take on the bulk o
     - A high-level description of the bug
     - Expected and Actual Results
     - Repro steps, including any TypeSpec code that you used
-    - Any error messages you saw, including stack traces. For issues with VS or VS Code tooling see [Troubleshooting VSCode Tooling and Filing Issues](#troubleshooting-vscode-tooling-and-filing-issues)
+    - Any error messages you saw, including stack traces. For issues with VS or VS Code tooling see [Troubleshooting VSCode Tooling and Filing Issues](../../typespec-getting-started.md#troubleshooting-vscode-tooling-and-filing-issues)
 - Schedule review meetings with TypeSpec team.

docs/intro.md

@@ -2,7 +2,7 @@
 
 TypeSpec is a language for describing cloud service APIs and generating other API description languages, client and service code, documentation, and other assets. TypeSpec provides highly extensible core language primitives that can describe API shapes common among REST, GraphQL, gRPC, and other protocols.
 
-You can find more information at https://microsoft.github.io/typespec.
+You can find more information at https://typespec.io/docs.
 
 This site is focused on using TypeSpec in the context of Azure. We have published a set of libraries with standard patterns and templates to make defining Azure management and data-plane services easy and compliant with Azure API guidelines. Using these building blocks
 and guard rails, your service API will be easier to build, will have an easier time passing API reviews, will be consistent with other Azure
@@ -47,7 +47,7 @@ for specific scenarios:
     - A high-level description of the bug
     - Expected and Actual Results
     - Repro steps, including any TypeSpec code that you used
-    - Any error messages you saw, including stack traces. For issues with VS or VS Code tooling see [Troubleshooting VSCode Tooling and Filing Issues](#troubleshooting-vscode-tooling-and-filing-issues)
+    - Any error messages you saw, including stack traces. For issues with VS or VS Code tooling see [Troubleshooting VSCode Tooling and Filing Issues](./typespec-getting-started.md#troubleshooting-vscode-tooling-and-filing-issues)
 
 ## More Information About TypeSpec
 

docs/reference/azure-style-guide.md

@@ -50,7 +50,7 @@ in Azure TypeSpec definitions.
   Instead, we recommend using supported scalars. Azure-specific scalars include: `eTag`, `ipV4Address`, `ipV6Address` and `uuid`. General
   TypeSpec scalars include: `bytes`, `numeric`, `integer`, `float`, `int64`, `int32`, `int16`, `int8`, `uint64`, `uint32`, `uint16`, `uint8`,
   `safeint`, `float64`, `float32`, `decimal`, `decimal128`, `string`, `plainDate`, `plainTime`, `utcDateTime`, `offsetDateTime`, `duration`,
-  `boolean`, and `url`. For more information, see the document on [Types Relations](https://microsoft.github.io/typespec/language-basics/type-relations)
+  `boolean`, and `url`. For more information, see the document on [Types Relations](https://typespec.io/docs/language-basics/type-relations)
 
 ## Operation Groups
 

docs/release-notes/release-2022-10-12.md

@@ -6,7 +6,7 @@ title: October 2022
 
 This release contains **breaking changes**
 
-Change to compiler, rest libraries [See TypeSpec Core release notes](https://microsoft.github.io/typespec/docs/release-notes/release-2022-10-12/)
+Change to compiler, rest libraries [See TypeSpec Core release notes](https://typespec.io/docs/release-notes/release-2022-10-12/)
 
 - **`TypeSpec`**: Cannot `extends` or `is` a model expression via alias
 - **`Api`**: Removed `createProgram` and changed `compile` parameter order