Fix additional schema paths

- Remove obsolete travis build badge.

.github/workflows/release.yml

@@ -338,7 +338,7 @@ jobs:
       - env:
           GITHUB_TOKEN: ${{ secrets.PULUMI_BOT_TOKEN }}
         name: Dispatch event
-        run: pulumictl create docs-build pulumi-${{ env.PROVIDER }} ${GITHUB_REF#refs/tags/} --schema-path awsx/schema.json
+        run: pulumictl create docs-build pulumi-${{ env.PROVIDER }} ${GITHUB_REF#refs/tags/} --schema-path schema.json
 name: release
 "on":
   push:

DEVELOPMENT.md

@@ -1,5 +1,3 @@
-[![Build Status](https://travis-ci.com/pulumi/pulumi-awsx.svg?token=eHg7Zp5zdDDJfTjY8ejq&branch=master)](https://travis-ci.com/pulumi/pulumi-awsx)
-
 # Developing AWSX components
 
 ## Prerequisites
@@ -37,9 +35,9 @@ For building the SDKs:
 
 ### Implementing New Components
 
-The schema (`awsx/schema.json`) is generated by schemagen. The entry point is `schemagen/pkg/gen/schema.go`. Amend the go code to generate the schema for the component with its inputs, outputs and any relevant types. Run `make schema` to test your changes.
+The schema (`schema.json`) is generated by schemagen. The entry point is `schemagen/pkg/gen/schema.go`. Amend the go code to generate the schema for the component with its inputs, outputs and any relevant types. Run `make schema` to test your changes.
 
-From the `awsx/schema.json` we generate provider types (`awsx/schema-types.ts`) which describe the interfaces that the provider must implement. Running `make provider` will automatically re-generate this as needed.
+From the `schema.json` we generate provider types (`awsx/schema-types.ts`) which describe the interfaces that the provider must implement. Running `make provider` will automatically re-generate this as needed.
 
 To implement a new provider resource:
 
@@ -51,7 +49,7 @@ To implement a new provider resource:
 
 2. Register the new component implementation in `awsx/resources.ts`.
 
-The SDKs are also generated from the `awsx/schema.json` using the `schemagen` program. This can be done by calling `make build`.
+The SDKs are also generated from the `schema.json` using the `schemagen` program. This can be done by calling `make build`.
 
 ## Testing Workflow